Designing Disaster Recovery Clusters using Metroclusters and Continentalclusters, Reprinted October 2011 (5900-1881)

information on configuring Oracle RAC, refer to the Oracle RAC installation and configuration
user’s guide.
If you have Oracle Clusterware and Serviceguard running in your environment, you need to
complete certain additional configuration procedures. For more information on these
configuration procedures, see “Serviceguard/Serviceguard Extension for RAC and Oracle
Clusterware Configuration” (page 121).
4. Configure Continentalclusters. For more information on configuring Continentalclusters, see
“Building the Continentalclusters Configuration” (page 58).
5. Configure Oracle RAC instances in Serviceguard packages. Continentalclusters supports
recovery only for applications running in Serviceguard packages. In a multiple recovery pair
scenario, where more than one primary cluster share the same recovery cluster, the primary
RAC instance package name must be unique on each primary cluster.
Configure the Oracle RAC instance packages on both primary and recovery clusters based
on the number of RAC instances configured to run on that cluster. Ensure that the same number
of Oracle RAC instances are configured on both the primary and recovery clusters. This ensures
Continentalclusters recovery protection. Set the AUTO_RUN parameter in the package
configuration file to NO.
In the Continentalclusters environment, the RAC database can be configured using the HP
Serviceguard extension for RAC (SGeRAC) toolkit. In addition, the RAC database can be
configured either as a legacy package or a modular package. For more information on
configuring the RAC database as a multi-node package, see the Using Serviceguard Extension
for RAC user’s guide.
NOTE: While configuring the RAC database as a modular package, do not use the
pre-integrated physical replication modules, such as ccxpca, cccaeva, and ccsrdf.
6. Setup the environment file. Instead of one environment file for each Continentalclusters
application package, there is only one environment file for each set of Oracle RAC instance
packages accessing the same database. This file can be located anywhere except the directory
where the Oracle RAC instance package configuration and control files reside. Only one
environment file can reside under one directory. The setup of the file is the same as what is
described in section, “Physical Data Replication ” (page 50) of this chapter, with the exception
of the PKGDIRvariable.
The value of the PKGDIR variable must be the directory where this environment file resides.
For specific information on how to setup the environment file, see Chapter 3 under section,
“Configuring Legacy Packages for Disaster Recovery” Chapter 4 under section, “Configuring
Legacy Packages for Automatic Disaster Recovery” or Chapter 5 under section “Configuring
Serviceguard Legacy Packages for Automatic Disaster Recovery”.
Be sure to place this environment file in the same path on all nodes of both the primary and
recovery clusters in a recovery pair. You must name the environment file using your package
name as the prefix. For example, <package name>_xpca.env. You must uncomment all
the AUTO variables in the environment file.
Based on the disk arrays in your environment, refer to the corresponding chapters of this
manual for more information on configuring the environment file for your storage.
7. Set up the Continentalclusters Oracle RAC specification file. The existence of file /etc/
cmconcl/ccrac/ccrac.config servers as an enabler for Continentalclusters Oracle RAC
support. A template of this file is available in /opt/cmconcl/scripts directory.
Edit this file to suit your environment. After editing, move the file to /etc/cmconcl/ccrac/
ccrac.config directory on all nodes in the participating clusters. Use the following steps
to set up the file:
Support for Oracle RAC Instances in a Continentalclusters Environment 117