Serviceguard/Serviceguard Extension for RAC and Oracle Clusterware Configuration

The following are the required configurations for Continentalclusters RAC instance recovery support for the cluster environment running with Serviceguard/Serviceguard Extension for RAC and CRS (Oracle Cluster Software):

1.The Oracle RAC environment running with Serviceguard/Serviceguard Extension for RAC and Oracle Cluster Software should follow all the recommendations listed in the Serviceguard and SGeRAC manuals for running with CRS (Oracle Cluster Software).

2.CRS should not activate the volume groups configured for the database automatically at startup time. The file /var/opt/oracle/oravg.conf should not exist on any node of the primary and recovery cluster.

3.The CRS storage (OCR and voting disk) should be configured on a separate volume group than the ones for the databases which are to be accessed by the RAC instances.

4.The RAC instance attribute AUTO_START listed in the CRS service profile should be set to 2 on both primary and recovery clusters so that the instance will not be automatically started when the node rejoins the cluster. Login as the oracle administrator and use the following steps to change the attribute value:

a.Generate the resource profile.

crs_stat -p instance_name > $CRS_HOME/crs/public/instance_name.cap

b.Edit the resource profile and set AUTO_START value to 2.

c.Register the value.

crs_register -u instance_name

d.Verify the value.

crs_stat -p instance_name

Initial Startup of Oracle RAC Instance in a Continentalclusters Environment

To ensure that the disk array will be ready for access in shared mode for the Oracle RAC instances, it is recommended that the user runs the Continentalclusters tool /opt/cmconcl/bin/ ccrac_mgmt.ksh to initially startup the configured instance packages. This tool ensures that the configured disk array will be ready in writable mode for shared access before starting up the RAC instance packages. If this tool is not used, manual checking is needed to make sure the storage is ready in writable and shared access mode before starting the RAC instance packages.

NOTE: It is recommended that ccrac_mgmt.ksh is used for the initial startup of the RAC instance package, or for failing back the RAC instance packages. This tool should not be used at the recovery site for recovering RAC instance packages, instead cmrecovercl is used in this case.

After the initial startup, use Serviceguard commands cmhaltpkg, cmrunpkg, cmmodpkg as needed to halt and restart the packages on the primary cluster.

Use the following steps on any node of the primary cluster to do the initial startup of the Oracle RAC instance packages:

1.If the cluster is running with Serviceguard and Oracle CRS, make sure that the CRS daemons and the required Oracle services, such as listener, GSD, ONS, and VIP are up and running on all the nodes the RAC database instances are configured to run.

2.Make sure /etc/cmconcl/ccrac/ccrac.config exists and was edited to contain the appropriate information.

3.To start all the RAC instance packages configured to run as primary packages on the local cluster.

# /opt/cmconcl/bin/ccrac_mgmt.ksh start

To start a specific set of RAC instance packages.

Support for Oracle RAC Instances in a Continentalclusters Environment 121