Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy

9. Edit the tnsnames.ora file on the local nodes and modify the HOST = keywords to specify
node names of this site.
In this example, you must edit the tnsnames.ora file on the local nodes, SJC_1 and SJC_2.
10. Register the database with the CRS sub-cluster on remote site.
# srvctl add database -d hrdb -o /opt/app/oracle/product/10.2.0/db_1/
# srvctl add instance -d hrdb -i hrdb1 -n SJC_1
# srvctl add instance -d hrdb -i hrdb2 -n SJC_2
After registering the database with the CRS sub-cluster on the remote site, you can run the srvctl
status command to view the health of the database.
Configuring the RAC MNP stack at the recovery cluster
The RAC database must be packaged as Serviceguard MNP packages. You must configure the
RAC MNP package to have a dependency on the site Clusterware sub-cluster MNP package. This
step creates the RAC MNP stack at the target site that is configured to be managed by the Site
Controller Package. For more information on configuring the RAC database in MNP packages,
see the Serviceguard Extension for Oracle RAC toolkit README.
Halting the RAC database on the recovery cluster
You must halt the RAC database on the Target Disk Site so that it can be restarted at the source
disk site. Use the cmhaltpkg command to halt the RAC MNP stack on the replication Target Disk
Site node. Deport the disk groups at the replication Target Disk Site nodes using the vxdg deport
command.
Configuring an empty Site Controller package
The Site Controller package and the Site Safety Latch for the disaster tolerant RAC database are
the final two components to be configured. This section describes the procedure to configure the
Site Controller package in a Metrocluster.
To configure the Site Controller package:
1. From any node, create a Site Controller package configuration file using the dts/sc module:
# cmmakepkg -m dts/sc -m dts/mc3parrc
/etc/cmcluster/hrdb_sc/hrdb_sc.config
2. Edit the hrdb_sc.config file and specify a name for the package_name attribute:
package_name hrdb_sc
3. Edit the hrdb_sc.config file and specify the node_name parameter explicitly.
node_name SFO_1
node_name SFO_2
node_name SJC_1
node_name SJC_2
4. Edit the hrdb_sc.config file and specify the directory created in step 1 for the
dts/dts/dts_pkg_dir attribute.
dts/dts/dts_pkg_dir /etc/cmcluster/hrdb_sc
5. Specify a name for the log file. HP recommends that this file be located in the dts/dts/
dts_pkg_dir directory.
script_log_file /etc/cmcluster/hrdb_sc/hrdb_sc.log
6. Specify the sites without any packages. Do not specify any critical_package or
managed_package.
site san_francisco
site san_jose
90 Configuring Oracle RAC in SADTA