6.Run the following command at the remote site.
#chown -R oracle:oinstall /opt/app/oracle/admin/hrdb
7.Log in to any of the nodes in the remote site using the oracle user credentials.
#su – oracle
8.Configure a listener for the database on this site using the Oracle Network Configuration Assistant (NETCA).
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 will 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 in the recovery cluster and modify the HOST = keywords to suit the recovery cluster environment.
In this example, you must edit the tnsnames.ora file on every node in this site.
11.Register the database with the CRS on recovery cluster.
#srvctl add database
#srvctl add instance
#srvctl add instance
After registering the database with the CRS on the recovery cluster, you can view the health status of the database by running the following command:
# srvctl status
Configuring the Site Controller package in 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 complex workload in Continentalclusters using SADTA. For more information on configuring the Site Controller Package for Oracle RAC database with ASM in SADTA, see “Configuring the Site Controller package in the recovery cluster” (page 52).
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.
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>
142 Configuring Oracle RAC database with ASM in Continentalclusters using SADTA
