The Oracle installation process has been rewritten and largely simplified. It is no longer needed to create an intermediate ISO image. The required version is now automagically detected from the uploaded ZIP files.
For installing and configuring an Oracle database, a number of steps need to be done:
- Verify sizing requirements
- Installing the outrun-oracle RPM package
- Upload Oracle ZIP files using Anonymous FTP
- Running make-oracle
- running clusterware setup
- Creating ASM volumes
- Creating ASM diskgroups
- Creating a database
- Setup autostart for databases
- Configure DB console (11g only)
Installing Outrun Oracle package
To prepare Outrun for running Oracle, you need to install the RPM package outrun-oracle.
- Via the menu, shortcut
- Main menu ⟹ System ⟹ Oracle
- Via the menu, manual package selection
- Main menu ⟹ System ⟹ Install
- Then select outrun-oracle
- Via the CLI
yum install outrun-oracle
The reason this package is not installed by default, is that Outrun may serve other purposes as well. One purpose is that it might be deployed as a PXE install server. In future versions there might be packages for other (non-database) purposes, such as running Enterprise Manager middleware.
Before you can run the install procedure, Outrun checks a number of things to make sure the Oracle installer does not abort due to not meeting certain requirements.
The Install menu shows the result of these checks - Preinstall: OK (or WARNING or FAILED)
Checks: OK Version: Free: 20438 MB Installed: -
You can run the checks procedure (menu "Checks" to see the result of testing the prerequisites. All checks should have "Status OK". Status "ERROR" means the install cannot proceed.
|/u01 free space||/u01 must have at least 5500 MB free space|
|/tmp free space||/tmp must have at least 100MB free space|
|Memory||System must have at least 4GB memory. Note that depending on Oracle version you may get warnings during install if RAM is less than 8GB|
|Swap||Swapspace should be at least the size of RAM or more than 16GB|
|shared memory (kernel.shmmax)||Shared memory setting in sysctl should be at least half the RAM|
|NTP daemon||NTPd should be running|
|NTP time drift||NTP time drift should be less than 2000 seconds. If NTP is running but time drift is too large (usually shortly after reboot) then just wait a few minutes.|
|SCSI UUID||SCSI devices should report their UUID (using scsi_id --whitelisted /dev/<disk>. Strictly not an Oracle requirement but is needed for asmdisks(1)|
Downloading the ZIP files from Oracle
- We need certain patch sets from Oracle. The patch sets provide complete Oracle installation trees, you don't have to download the previous version as they are not needed.
- You need a valid user account and password for support.oracle.com.
- The ZIP files must be downloaded to your desktop first before uploading them to Outrun. Use your normal browser for this.
- Download site
- Log in to Oracle Support
- Download location
- On My Oracle Support go to tab "Patches & Updates"
- Under "Oracle Server and Tools" click "Latest patchsets"
- Go to "Oracle Database - Linux x86-64 – <version>"
Supported versions in Outrun:
|Oracle Patch Sets|
|184.108.40.206.0||Oracle Database Patch Set 10404530||ZIP file #1, #2, #3 of 7||recommended|
|220.127.116.11.0||Oracle Database Patch Set 13390677||ZIP file #1, #2, #3 of 7||Obsolete|
|18.104.22.168.0||Oracle Database Patch Set 17694377||only if you need 12c||Lacks DBconsole|
|22.214.171.124.4||Oracle Database Install files||only if you need 12c||Lacks DBconsole|
Uploading the ZIP files to Outrun
After installation, Outrun configures an embedded FTP server based on vsftpd. The server is only started when a connection is made so it's very lightweight.The folder
/var/ftp/oracleis configured as upload location and does not require a userid or password. It does however require an FTP client that can handle secure SSL connections (most Internet browsers can only download stuff). When connecting with FTP the upload folder shows as
- Upload the ZIP files for the required version to the Outrun system's FTP incoming folder
Running the Oracle Install
If the ZIP files are uploaded to FTP and the pre-install checks are OK, you may proceed to install Oracle.
This is done via an Oracle installer feature named "silent install" which means you don't need to enter details via a wizard, everything is pre-defined. The definitions are listed in what is called a "response file" - Outrun includes response files for the various Oracle versions.
You have the option to install from the command-line or via the menu. In both cases a Makefile script called 'make-oracle' will be executed.
Running from menu
- From the main menu, select 'Install'
- From the Install menu, select 'Install Database Server'
Running from CLI
If you want to run install from the CLI, use the command
Setup clusterware and ASM
After the software installation is complete, you need to setup Clusterware and Oracle ASM (even if you don't want to run multi-node clusters or Oracle RAC). Clusterware is a pre-requisite for Oracle ASM and manages starting/stopping/monitoring of server processes.
NOTE: Oracle RAC is not yet (fully) supported in Outrun. So you will only have the "single node" options available.
NOTE: The Clusterware setup options don't appear in the menu if Oracle was not installed properly.
You should see the output of the setup process showing something like this:
Successfully configured Oracle Grid Infrastructure for a Standalone Server NAME TARGET STATE SERVER STATE_DETAILS Local Resources ora.LISTENER.lsnr ONLINE ONLINE outrun01 ora.ons OFFLINE OFFLINE outrun01 Cluster Resources ora.cssd 1 OFFLINE OFFLINE ora.diskmon 1 OFFLINE OFFLINE ora.evmd 1 ONLINE INTERMEDIATE outrun01
At this point, clusterware services are starting and you may configure Oracle ASM. Choose "ASM" from the menu. CLI alternative:
If ASM configured correctly, you have finished Outrun setup and the Oracle install phase and you're ready to create a database.
You may verify the status of Clusterware and ASM by running "Status" from the Install menu. CLI alternative:
CRS-4638: Oracle High Availability Services is online NAME TARGET STATE SERVER STATE_DETAILS Local Resources ora.LISTENER.lsnr ONLINE ONLINE outrun01 ora.asm ONLINE ONLINE outrun01 Started ora.ons OFFLINE OFFLINE outrun01 Cluster Resources ora.cssd 1 ONLINE ONLINE outrun01 ora.diskmon 1 OFFLINE OFFLINE ora.evmd 1 ONLINE ONLINE outrun01
Note that the resources "ora.ons" and "ora.diskmon" are OFFLINE - this is normal. The other resources should be in state ONLINE.
Creating RPM package
The install procedure can also create an RPM package containing the entire Oracle installation. This makes it possible to install multiple servers simply by running
yum install oracle-<version>
Creating the RPM requires the rpm-build package to be installed. You also need a lot of space on /var (usually at least 4-5 GB) and on /u01 (also at least 4-5 GB).
To crate the package, run:
The Oracle installer is very sensitive to minor errors or preconditions. The Outrun Checks procedure attempts to catch the most common problems and Outrun in general is designed to make installation failproof due to locked down dependencies, dynamic system configuration (such as kernel settings, ulimits, memory tuning etc). However, the devil is in the details and the install might not finish without errors. To make things worse, the error messages are very obscure (especially using the silent installer) and log files tend to be very hard to digest and sometimes they are deleted before you get a chance to inspect them.
It is possible you run into such problems even when the preinstall checks shows OK status. I would like to hear such problems so I can catch the error before the installer gives up. If you feel adventurous you may attempt to run the graphical installer yourself as it is a little more useful in showing things that went wrong. Procedure for manual GUI install:
- install the "lightvnc" rpm package
- Open a VNC session on port 5900, login as "grid" (for clusterware) or as "oracle" (for database install)
- Open a shell (right mouse button)
- run make-oracle unzip
- run /uu1/tmp/staging/grid/runInstaller for grid/clusterware install (note for 12.2+ you need to manually unzip)
- run /u01/tmp/staging/database/runInstaller for database install
- work through the GUI and see why the install fails
Instead of installing lightvnc you can also remote connect with an X forwarding session from a Linux workstation:
ssh -X grid@<server>