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

9. Copy the tnsnames.ora file from the primary cluster CRS and modify it to fit the local
environment.
In this example, the file contents would appear as follows:
rcp <cluster1_node1>:$ORACLE_HOME/network/admin/tnsnames.ora
<cluster2_node1>:$ORACLE_HOME/network/admin/tnsnames.ora
rcp <cluster1_node2>:$ORACLE_HOME/network/admin/tnsnames.ora
<cluster2_node2>:$ORACLE_HOME/network/admin/tnsnames.ora
10. Edit the tnsnames.ora file on the nodes at the recovery cluster and modify the HOST =
keywordsto suit the recovery cluster environment.
In this example, you must edit the tnsnames.ora file on each node in this site.
11. Register the database with the CRS on recovery cluster.
srvctl add database -d hrdb -o /opt/app/oracle/product/11.1.0/db_1/
srvctl add instance -d hrdb -i hrdb1 -n <cluster2_node1>
srvctl add instance -d hrdb -i hrdb2 -n <cluster2_node2>
After registering the database with the CRS on the recovery cluster, you can run the
srvctl status
command to view the health of the database.
Configuring the Site Controller Package at the primary cluster
The site controller package needs to be configured in the primary cluster.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 with Complex Workload packages in the
Primary Cluster” (page 137)
Configuring the Site Safety Latch Dependencies at the primary cluster
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 in the primary
cluster:
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 in primary cluster with the RAC MNP stack in primary
cluster:
site cc1_site1
critical_package <cluster1_RAC_DB_pkg_name>
managed_package <cluster1_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>
Configuring Oracle RAC Database with ASM in a Site Aware Disaster Tolerant Architecture 149