Oracle RAC - Database software installer answers

category: solutionz · date: 2016-12-31 · updated: 2026-10-02 · author: LALA

Oracle RAC Solution · Config document · referenced from Database software, listener and disk groups

note<ORACLE_OS_PASSWORD> is a placeholder for the operating system password of the user oracle. The installer asks for it once, to set up SSH between the nodes.

The answers given to the graphical installer of Oracle Database 11.2.0.4 (runInstaller), screen by screen, as my working notes hold them. The installer puts the database software, and nothing else, on both nodes; the database itself comes later from DBCA.

Item	Value
Tool	`/data/install/database/runInstaller`
Started on	the notes do not name the node; `oradb01` by inference from the later steps. As `oracle`, with an X server running on the workstation the installation was driven from
Installs to	`oradb01` and `oradb02`
Oracle base	`/data/u01/app/oracle`
Oracle home	`/data/u01/app/oracle/db11204`
Owner	`oracle`, primary group `oinstall`, secondary groups `asmdba` and `dba`
Inventory	`/data/u01/app/oraInventory`
Software version at the time	Oracle Database 11.2.0.4, Standard Edition

The answers

ini

# Screen / Field = value, in the order of the installer screens.
# "checked" and "unchecked" are the state of a check box or radio button.

Configure Security Updates / Email = oraadmin@example.net
Configure Security Updates / I wish to receive security updates via My Oracle Support = unchecked, nothing filled in

# The installer could not reach My Oracle Support and showed this dialogue.
Connection Failed / Connection Method = Proxy
Connection Failed / I want to remain uninformed of critical security issues in my configuration = checked

Download Software Updates / Skip software updates = checked

Installation Option / Install database software only = checked

Grid Installation Options / Oracle Real Application Cluster database installation = checked
Grid Installation Options / Select nodes = oradb01, oradb02

# Select both nodes, fill in the values, press "Setup", then "Test".
SSH Connectivity / OS Username = oracle
SSH Connectivity / OS Password = <ORACLE_OS_PASSWORD>
SSH Connectivity / User home is shared by the selected nodes = unchecked
SSH Connectivity / Reuse private and public keys existing in the user home = checked

Product Languages / Selected Languages = English

Database Edition / Standard Edition (4,6 GB) = checked

Installation Location / Oracle Base = /data/u01/app/oracle
Installation Location / Software Location = /data/u01/app/oracle/db11204

Operating System Groups / Database Administrator (OSDBA) Group = dba
Operating System Groups / Database Operator (OSOPER) Group (Optional) = oinstall

Summary / Install = clicked

Answer	What it means
Install database software only	No database and no listener are created by the installer. Both were done with their own tools afterwards
Oracle Real Application Cluster database installation, both nodes	The installer copies the home to `oradb02` over SSH and links the RAC option on both nodes
Reuse private and public keys	The keys of `oracle` were generated during the operating system preparation; the installer only distributes them
OSOPER = `oinstall`	Every member of the installation group gets the operator privilege. The notes give no reason for the choice; the Grid Infrastructure installer was answered the same way for its operator group

The root.sh run

Towards the end the installer asked for one script to be run as root on both nodes, on oradb01 first and then on oradb02.

bash

$ /data/u01/app/oracle/db11204/root.sh

output 16 lines

Performing root user operation for Oracle 11g

The following environment variables are set as:
    ORACLE_OWNER= oracle
    ORACLE_HOME=  /data/u01/app/oracle/db11204

Enter the full pathname of the local bin directory: [/usr/local/bin]:
The contents of "dbhome" have not changed. No need to overwrite.
The contents of "oraenv" have not changed. No need to overwrite.
The contents of "coraenv" have not changed. No need to overwrite.

Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
Finished product-specific root actions.

The notes hold one copy of the output for both nodes. The three "have not changed" lines are there because root.sh of the Grid Infrastructure home had already put dbhome, oraenv and coraenv into /usr/local/bin. The prerequisite check screen of this installer is not in the notes.

Checked against Oracle AI Database 26ai

As built	Today
Oracle Database 11g Release 2 (11.2.0.4)	Premier Support for 11.2 ended in January 2015 and Extended Support in December 2020. The current release is Oracle AI Database 26ai; 19c is the other long term support release
`./runInstaller` from unpacked installation media, which copies the software into a new home	Image-based since 18c: the image is extracted into the new Oracle home and the setup wizard (`runInstaller` inside that home) is run there
Standard Edition with RAC	The old Standard Edition ended with 12.1.0.1 and was followed by Standard Edition 2. From 19c RAC is not supported in Standard Edition 2; the replacement is Standard Edition High Availability, a cluster-based failover for a single instance. In the 26ai licensing manual RAC is an extra cost option of Enterprise Edition
SSH Connectivity, "Setup" with reuse of existing keys	The installer's automatic setup creates RSA keys, in 11.2 and in 26ai. The DSA keys generated beside them during the preparation were never needed, and OpenSSH 10.0 removed DSA
OSDBA `dba`, OSOPER `oinstall`	The OSOPER group is still optional. Since 12c there are four more groups for separated duties, typically `backupdba`, `dgdba`, `kmdba` and (since 12.2) `racdba`

The answer set cannot be repeated on current software: the edition and feature combination chosen here, Standard Edition with RAC, no longer exists.