This section contains the procedure that you need to install Oracle software.
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.
Before you start the Oracle installation, ensure that the system resources required for Oracle have been configured. 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.
You could use Solaris Resource Management (SRM) to ensure that the kernel parameters are set to at least the minimum values that Oracle requires. For more information about setting the Oracle kernel parameters, see How to Set the Oracle Kernel Parameters. After the system resources have been configured for Oracle you can start the installation itself.
If you are using HA for Oracle with Oracle 10g release 2, omit this step.
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
HA for Oracle does not require the Oracle cssd daemon. Therefore, removal of this entry does not affect the operation of Oracle 10g release 1 with 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 RAC 10g release 1, 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 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 Oracle Solaris Cluster controls are never mounted.
A node is booting. In this situation, the messages are displayed repeatedly until Oracle Solaris Cluster mounts the file system where the Oracle binary files are installed.
Oracle is started on or fails over to a node or zone 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 or zone where the Oracle installation was run.
The default project is modified to contain the resources required for Oracle as the RGM uses the default project for running the data service. If you want to use a specific SRM project for running Oracle, you must create that project and configure the system resources in that project using the same procedure. Specify the project name instead of default. When you configure the resource group or resource for the Oracle server, specify that project name in the corresponding property of the resource group or resource.
phys-X# prctl -i project default
phys-X# projmod -s -K "parameter=(priv,value,deny)" default
See the Oracle10g Installation Guide for more information about these parameters.
phys-X# prctl -i project default