Installing the Oracle Software

This section contains the procedure that you need to install Oracle software.

How to Install the Oracle Software

Steps

1. Become superuser on a cluster member.

2. If you plan to install the Oracle software on the cluster file system, start the Sun Cluster software and become the owner of the disk device group.

   If you plan to install the Oracle software at another location, omit this step.

   For more information about installation locations, see Preparing the Nodes and Disks.

3. Install the Oracle software.

   Regardless of where you install the Oracle software, modify each node's /etc/system files as you would in standard Oracle installation procedures. Then reboot.

   Log in as oracle to ensure ownership of the entire directory before you perform this step. See the appropriate Oracle installation and configuration guides for instructions about how to install Oracle software.

4. (Optional) If you are using Sun Cluster HA for Oracle with Oracle 10g, prevent the Oracle cssd daemon from being started.

   Remove the entry for the Oracle cssd daemon from the /etc/inittab file on the node where the Oracle software is installed. To remove this entry, remove the following line from the /etc/inittab file:

   h1:23:respawn:/etc/init.d/init.cssd run >/dev/null 2>&1 > </dev/null

   Sun Cluster HA for Oracle does not require the Oracle cssd daemon. Therefore, removal of this entry does not affect the operation of Oracle 10g with Sun Cluster HA for Oracle. If your Oracle installation changes so that the Oracle cssd daemon is required, restore the entry for this daemon to the /etc/inittab file.

   ---

   Caution –

   If you are using Oracle 10g Real Application Clusters, do not remove the entry for the cssd daemon from the /etc/inittab file.

   ---

   If you remove the entry for the Oracle cssd daemon from the /etc/inittab file, you prevent unnecessary error messages from being displayed. Otherwise, an attempt by the init(1M) command to start the Oracle cssd daemon might cause such error messages to be displayed. These error messages are displayed if the Oracle binary files are installed on a highly available local file system or on the cluster file system. The messages are displayed repeatedly until the file system where the Oracle binary files are installed is mounted.

   These error messages are as follows:

   INIT: Command is respawning too rapidly. Check for possible errors. id: h1 "/etc/init.d/init.cssd run >/dev/null 2>&1 >/dev/null"

   Waiting for filesystem containing $CRSCTL.

   If you are using Sun Cluster HA for Oracle on the x86 platform, unnecessary error messages about the unavailability of the UNIX Distributed Lock Manager (Oracle UDLM) might also be displayed.

   These messages are displayed if the following events occur:

   • A node is running in noncluster mode. In this situation, file systems that Sun Cluster controls are never mounted.

   • A node is booting. In this situation, the messages are displayed repeatedly until Sun Cluster mounts the file system where the Oracle binary files are installed.

   • Oracle is started on or fails over to a node where the Oracle installation was not originally run. In such a configuration, the Oracle binary files are installed on a highly available local file system. In this situation, the messages are displayed on the console of the node where the Oracle installation was run.