Building Disaster Recovery Serviceguard Solutions Using Continentalclusters A.08.00

When you finish configuring a recovery pair with RAC support, your systems must have sets
of files similar to those shown in Figure 5.
NOTE: If you are configuring Oracle RAC instances in Serviceguard packages in a CFS or CVM
environment, do not specify the CVM_DISK_GROUPS, and CVM_ACTIVATION_CMD fields in the
package control scripts as CVM disk group manipulation is addressed by the disk group multi
node package.
Figure 5 Continentalclusters configuration files in a recovery pair with RAC support
NOTE: Starting from Continentalclusters Version A.08.00, there are no managed object files in
the /etc/cmconl/instances directory.
Serviceguard/Serviceguard extension for RAC and Oracle Clusterware configuration
The following configurations are required for Continentalclusters RAC instance recovery support
for the cluster environment that has with Serviceguard/Serviceguard Extension for RAC and CRS
(Oracle Cluster Software):
1. The Oracle RAC environment having Serviceguard/Serviceguard Extension for RAC and
Oracle Cluster Software must follow all the recommendations listed in the Serviceguard and
SGeRAC manuals for running with CRS (Oracle Cluster Software).
2. At start up, CRS must not automatically activate the volume groups that are configured for the
database. The file /var/opt/oracle/oravg.conf must not exist on any node of the
primary and recovery cluster.
3. The CRS storage (OCR and voting disk) must be configured on a separate volume group that
is separate from the databases which are accessed by the RAC instances.
4. The RAC instance attribute AUTO_START listed in the CRS service profile must be set to 2 on
both primary and recovery clusters so that the instance does not automatically start when the
node rejoins the cluster. Log in as the oracle administrator and change the attribute value:
Support for Oracle RAC instances in a Continentalclusters environment 131