08 Install ASM Software
07 Oracle Clusterware Postinstallation Procedures
09 Install Oracle Database Software

References

Oracle® Real Application Clusters Installation Guide 11g Release 1 (11.1) for Linux and UNIX

Overview

The installation of the Oracle software will be done twice:

  1. ASM will be Oracle Database Software installed into its own home with asm as the owner;
  2. Oracle Database Software installed into its own home with oracle as the owner

Preinstallation Checklist

Reviewed the Preinstallation Checklist . Most of this was done in the establishment of the Oracle Clusterware configuration.

Confirming Cluster Readiness for Oracle RAC Installation with CVU

Followed the procedure in Confirming Cluster Readiness for Oracle RAC Installation with CVU , by running as the asm user,: 

su - asm
/u00/product/11.1.0.6/clusterware/runcluvfy.sh stage -pre dbinst -n penrith1,penrith2 \
-osdba asmdba -verbose >/tmp/cluvfy_pre_dbinst.lst

The log has been uploaded as cluvfy_pre_dbinst.lst . The only issue is memory size again. This does not seem to be a problem for OUI.

Installing Oracle Database 11g with Oracle Real Application Clusters

Reviewed nstalling Oracle Database 11g with Oracle Real Application Clusters .

Verifying System Readiness for Installing Oracle Database with CVU

CVU has already been done. The documentation is really insistent on this step!

Reviewing Oracle Application Express Requirements

APEX is not applicable.

Selecting a Configuration Option

The Configuration Option for both ASM and Database installation is Install database software only .

As a result, the following sections are not applicable to this installation:

  • Automatic Storage Management Configuration
  • Preparing for a Rolling Upgrade of Automatic Storage Management
  • Oracle Database Vault Configuration
  • Oracle Database Configuration Type Descriptions
  • Oracle Configuration Manager Option
  • Database Security Options
  • Selecting Database Passwords
  • Actions of OUI, DBCA, and Other Assistants During Installation
  • Installing Oracle Database with Other Languages
  • Selecting a Database Name
Using Oracle Universal Installer to install Oracle RAC 
su - asm
cd /u00/product/11.1.0.6/database
./runInstaller.sh
  • ORACLE_BASE is /u01/app/asm .
  • ORACLE_HOME is /u01/app/asm/product/11.1.0/db_1 .
Run root.sh Scripts

On PENRITH1 , 

[root@penrith1 logs]# cd /u01/app/asm/product/11.1.0/db_1/
[root@penrith1 db_1]# ./root.sh
Running Oracle 11g root.sh script...

The following environment variables are set as:
    ORACLE_OWNER= asm
    ORACLE_HOME=  /u01/app/asm/product/11.1.0/db_1

Enter the full pathname of the local bin directory: [/usr/local/bin]: 
   Copying dbhome to /usr/local/bin ...
   Copying oraenv to /usr/local/bin ...
   Copying coraenv to /usr/local/bin ...


Creating /etc/oratab file...
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.sh script.
Now product-specific root actions will be performed.
Finished product-specific root actions.

On PENRITH2 , 

[root@penrith2 ~]# cd /u01/app/asm/product/11.1.0/db_1/
[root@penrith2 db_1]# ./root.sh
Running Oracle 11g root.sh script...

The following environment variables are set as:
    ORACLE_OWNER= asm
    ORACLE_HOME=  /u01/app/asm/product/11.1.0/db_1

Enter the full pathname of the local bin directory: [/usr/local/bin]: 
   Copying dbhome to /usr/local/bin ...
   Copying oraenv to /usr/local/bin ...
   Copying coraenv to /usr/local/bin ...


Creating /etc/oratab file...
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.sh script.
Now product-specific root actions will be performed.
Finished product-specific root actions.
Check Installation of ASM

CLUVFY was used to validate the successful installation of the ASM software: 

su - asm
/u00/product/11.1.0.6/clusterware/runcluvfy.sh stage -pre dbcfg -n penrith1,penrith2 \
-d /u01/app/asm/product/11.1.0/db_1 -verbose >/tmp/cluvfy_pre_dbcfg.lst

The file, cluvfy_pre_dbcfg.lst , has been uploaded as an attachment.

And the root.sh script was backed up as follows on both PENRITH1 and PENRITH2 : 

[asm@penrith1 ~]$ mkdir -p backup/11.1.0.6
[asm@penrith1 ~]$ cp /u01/app/asm/product/11.1.0/db_1/root.sh backup/11.1.0.6/