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

the latest edition of the Using Serviceguard Extension for RAC manual, available at www.hp.com/
go/hpux-serviceguard-docs.
Configuring SGeRAC Toolkit Packages for the ASM disk group in the Primary cluster
To configure SADTA in Continentalclusters for Oracle RAC database with ASM, the ASM disk
group must be packaged in Serviceguard MNP packages in both clusters. Configure ASM Disk
group MNP package dependency on the Clusterware MNP package on both the clusters. For
information on configuring the ASM disk group in the Serviceguard MNP packages, see the HP
SGeRAC Toolkit README.
Creating the Oracle RAC Database in the Primary cluster
After setting up the ASM disk group for the RAC database data files, you must create the RAC
database. You can use the Oracle Database Configuration Assistant (DBCA) to create the RAC
database. After you login to the DBCA, select the Automatic Storage Management option as the
storage mechanism for the database and select the Use Oracle-managed files option to store
database files and provide the ASM DG that you created earlier.
Configuring and Testing the RAC MNP Stack at the Primary cluster
To configure Oracle RAC Database with ASM in SADTA, the RAC database must be packaged
in Serviceguard MNP packages in both clusters. Also, automatic startup of RAC database instances
and services at Clusterware startup must be disabled. For more information on disabling automatic
startup of RAC databases, see the How To Remove CRS Auto Start and Restart for a RAC Instance
document available at the Oracle documentation site. For information on configuring the RAC
database in the MNP packages, see the HP SGeRAC Toolkit README. Configure the RAC MNP
package to have dependency on the Clusterware MNP package and ASM disk group MNP
package. This step completes the configuration of the RAC MNP stack at the primary cluster. Ensure
that in RAC MNP package, the service is configured to monitor the Oracle RAC database. Before
halting the RAC MNP stack, test the configuration to ensure that the packages are configured
appropriately and can be started.
Halting the RAC Database on the Primary cluster
After creating the RAC database on the primary cluster, you must halt it to replicate it on the
recovery cluster. If you are using 11g R2 RAC, you must change the remote_listener for the database
before halting the RAC database MNP stack as explained in step 1.
1. When using Oracle 11g R2 with ASM, the remote_listener for the database is set to the
<SCAN name>: <port number>by default. But, in the Continentalclusters configuration, the
SCAN name is different for each cluster CRS. So, the remote_listener for the database must
be changed to the net service name configured in the tnsnames.ora for the database. This
task must be done prior to halting the RAC database stack on the Primary Cluster:
a. Log in as the Oracle user.
# su – oracle
b. Export the database instance on the node. In this example, hrdb1 is database instance
running on this node.
export ORACLE_SID=”hrdb1”
c. Alter the remote listener:
# sqlplus “/ as sysdba”
d. At the prompt, enter the following:
SQL>show parameter remote_listener;
SQL> alter system set remote_listener=’hrdb’
2. Halt the RAC MNP Stack on the replication primary cluster node:
146 Designing Continentalclusters