Using Serviceguard Extension for RAC, 9th Edition, September 2010
For CFS 5.0:
Oracle instance running with ODM: VERITAS 5.0 ODM Library, Version
1.0
Configuring Oracle to Stop using Oracle Disk Manager Library
NOTE: The following steps are specific to CFS 4.1 or later.
1. Login as Oracle user.
2. Shutdown the database.
3. Change directories:
$ cd ${ORACE_HOME}/lib
4. Remove the file linked to the ODM library:
For HP 9000 systems:
$ rm libodm9.sl
$ ln -s ${ORACLE_HOME}/lib/libodmd9.sl ${ORACLE_HOME}/lib/libodm9.sl
For Integrity systems:
$ rm libodm9.so
$ ln -s ${ORACLE_HOME}/lib/libodmd9.so ${ORACLE_HOME}/lib/libodm9.so
5. Restart the database.
Using Packages to Configure Startup and Shutdown of RAC Instances
To automate the startup and shutdown of RAC instances on the nodes of the cluster, you can
create packages that activate the appropriate volume groups and then run RAC. Refer to the
section “Creating Packages to Launch Oracle RAC Instances”.
NOTE: The maximum number of RAC instances for Oracle 9i is 127 per cluster. For Oracle
10g/11gR1/11gR2 refer to Oracle’s requirements.
Starting Oracle Instances
Once the Oracle installation is complete, ensure that all package control scripts are in place on
each node and that each /etc/rc.config.d/cmcluster script contains the entry
AUTOSTART_CMCLD=1. Then reboot each node. Within a couple of minutes following reboot,
the cluster will reform, and the package control scripts will bring up the database instances and
application programs.
When Oracle has been started, you can use the SAM process management area or the ps -ef
command on both nodes to verify that all RAC daemons and Oracle processes are running.
Starting Up and Shutting Down Manually
To start up and shut down RAC instances without using packages, you can perform the following
steps.
• Starting up involves the following sequence:
1. Start up the cluster (cmrunnode or cmruncl).
2. Activate the database volume groups or disk groups in shared mode.
3. Bring up Oracle in shared mode.
4. Bring up the Oracle applications, if any.
• Shutting down involves the following sequence:
Configuring Oracle to Stop using Oracle Disk Manager Library 103