Using Serviceguard Extension for RAC, 7th Edition, September 2008

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:
1. Shut down the Oracle applications, if any.
2. Shut down Oracle.
3. Deactivate the database volume groups or disk groups.
4. Shut down the cluster (cmhaltnode or cmhaltcl).
If the shutdown sequence described above is not followed, cmhaltcl or cmhaltnode may fail
with a message that GMS clients (RAC 9i) are active or that shared volume groups are active.
Creating Packages to Launch Oracle RAC Instances
To coordinate the startup and shutdown of RAC instances with cluster node startup and
shutdown, you create a one-node package for each node that runs an RAC instance. In the package
configuration file, you should specify only the single node on which the instance will run and
specify the control script that is to be executed every time the instance node or the entire RAC
cluster starts up or shuts down.
NOTE: You must create the RAC instance package with a PACKAGE_TYPE of FAILOVER, but
the fact that you are entering only one node ensures that the instance will only run on that node.
To simplify the creation of RAC instance packages, you can use the Oracle template provided
with the separately purchasable ECM Toolkits product (T1909BA). Use the special toolkit scripts
that are provided, and follow the instructions that appear in the README file. Also refer to the
section “Customizing the Control Script for RAC Instances” below for more information.
To create the package with Serviceguard Manager select the cluster. Go to the actions menu and
choose configure package. To modify a package, select the package. For an instance package,
create one package for each instance. On each node, supply the SID name for the package name.
To create a package on the command line, use the cmmakepkg command to get an editable
configuration file.
Set the AUTO_RUN parameter to YES,if you want the instance to start up as soon as the node
joins the cluster. In addition, you should set the NODE_FAILFAST_ENABLED parameter to NO.
If you are using CVM disk groups for the RAC database, be sure to include the name of each
disk group on a separate STORAGE_GROUP line in the configuration file.
If you are using CFS or CVM for RAC shared storage with multi-node packages, the package
containing the RAC instance should be configured with package dependency to depend on the
multi-node packages.
The following is a sample of the setup dependency conditions in application package configuration
file:
102 Serviceguard Configuration for Oracle 9i RAC