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

10. Edit the tnsnames.ora file on the nodes at the target disk site and modify the HOST =
keywords to suit the target disk site environment.
In this example, you must edit the tnsnames.ora file on each node in this site.
11. Register the database with the CRS sub-cluster on remote site.
srvctl add database -d hrdb -o /opt/app/oracle/product/11.1.0/db_1/
srvctl add instance -d hrdb -i hrdb1 -n <site2_node1>
srvctl add instance -d hrdb -i hrdb2 -n <site2_node2>
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 Site Controller Package
The procedure to configure the Site Controller Package is identical to the procedure in configuring
Oracle RAC in SADTA. For more information on configuring the Site Controller Package for Oracle
RAC database with ASM in SADTA, see “Configuring the Site Controller Package for the Complex
Workload” (page 355).
Configuring the Site Safety Latch Dependencies
After the Site Controller Package configuration is applied, the corresponding Site Safety Latch is
also configured automatically in the cluster. This section describes the procedure to configure the
Site Safety Latch dependencies.
Complete the following procedure to configure the Site Safety Latch dependencies:
1. Add the EMS resource details in ASM DG package configuration file.
RESOURCE_NAME /dts/mcsc/hrdb_sc
RESOURCE_POLLING_INTERVAL 120
RESOURCE_UP_VALUE != DOWN
RESOURCE_START automatic
You must apply the modified ASM DG package configuration using the cmapplyconf
command.
2. Verify the Site Safety Latch resource configuration at both sites.
Run the following command to view the EMS resource details:
# cmviewcl -v –p <ASM_DG_pkg_name>
3. Configure the Site Controller Package with the RAC MNP stack packages of both sites.
site site1
critical_package <site1_RAC_DB_pkg_name>
managed_package <site1_ASM_DG_pkg_name>
site site2
critical_package <site2_RAC_DB_pkg_name>
managed_package <site2_ASM_DG_pkg_name>
NOTE: Do not add any comments after specifying the critical and managed packages.
4. Re-apply the Site Controller Package configuration.
# cmapplyconf -v -P <site_controller_configuration_file>
After applying the Site Controller Package configuration, run the cmviewcl command to view the
packages that are configured.
390 Designing a Disaster Recovery Solution Using Site Aware Disaster Tolerant Architecture