Using Serviceguard Extension for RAC, 9th Edition, September 2010

Enter the names of the LVM volume groups you wish to activate in shared mode in the VG[]
array. Use a different array element for each RAC volume group. (Remember that RAC volume
groups must also be coded in the cluster configuration file using OPS_VOLUME_GROUP
parameters.) Be sure to specify shared activation with the vgchange command by setting the
VGCHANGE parameter as follows:
VGCHANGE="vgchange -a s”
If your disks are mirrored with LVM mirroring on separate physical paths and you want to
override quorum, use the following setting:
VGCHANGE="vgchange -a s -q n”
Enter the names of the CVM disk groups you wish to activate in shared mode in the CVM_DG[]
array. Use a different array element for each RAC disk group. (Remember that CVM disk groups
must also be coded in the package ASCII configuration file using STORAGE_GROUP parameters.)
Be sure to specify an appropriate type of shared activation with the CVM activation command.
For example:
CVM_ACTIVATION_CMD="vxdg -g \$DiskGroup set activation=sharedwrite"
Do not define the RAC instance as a package service. Instead, include the commands that start up a
RAC instance in the customer_defined_run_commands section of the package control script.
Similarly, you should include the commands that halt a RAC instance in the
customer_defined_halt_commands section of the package control script.
Define the Oracle monitoring command as a service command, or else use the special Oracle
script provided with the ECM Toolkit.
Using the Command Line to Configure an Oracle RAC Instance Package
Serviceguard Manager provides a template to configure package behavior that is specific to an
Oracle RAC Instance package. The RAC Instance package starts the Oracle RAC instance, monitors
the Oracle processes, and stops the RAC instance.
The configuration of the RAC Instance Package uses the Enterprise Cluster Master Toolkit (ECMT)
to start, monitor, and stop the Oracle database instance. For details on the use of ECMT, reference
ECMT documentation.
Each Oracle RAC database can have a database instance running on all nodes of a SGeRAC
cluster. Therefore, it is not necessary to failover the database instance to a different SGeRAC
node. This is the main difference between an Oracle RAC Instance Package and a single instance
Oracle package.
Information for Creating the Oracle RAC Instance Package on a SGeRAC Node
Use the following steps to set up the pre-package configuration on a SGeRAC node:
1. Gather the RAC Instance SID_NAME. If you are using Serviceguard Manager, this is in the
cluster Properties.
Example: SID_NAME=ORACLE_TEST0
For an ORACLE RAC instance, for a two-node cluster, each node would have an SID_NAME.
2. Gather the RAC Instance package name for each node that should be the same as the
SID_NAME for each node.
Example: ORACLE_TEST0
3. Gather the shared volume group name for the RAC database. In Serviceguard Manager, see
cluster Properties.
Example: /dev/vgora92db
4. Create the Oracle RAC Instance Package directory /etc/cmcluster/pkg/${SID_NAME}.
Example:/etc/cmcluster/pkg/ORACLE_TEST0
Using Packages to Configure Startup and Shutdown of RAC Instances 107