# cmhaltpkg <cluster1_rac_db_pkg> <cluster1_asmdg_pkg1>

Suspending the replication to the recovery cluster

In the earlier procedures, the RAC database and Site Controller packages were created at the primary cluster with the source disk of the replication disk group. A RAC MNP stack was also created at that cluster. Now, an identical RAC database using the target replicated disk must be configured with the RAC MNP stack in the recovery cluster.

Prior to setting up an identical RAC database at the recovery cluster, ensure that the Site Controller package is halted in the primary cluster. Split the data replication such that the target disk is in the Read/Write mode. The procedure to split the replication depends on the type of arrays that are configured in the environment. Based on the arrays in your environment, see the respective chapters of this manual to configure replication. After preparing the replicated disk at the recovery cluster, a storage device must be configured. For more information on configuring a storage device, see “Configuring the Storage Device for Complex Workload at the Recovery cluster” (page 138).

Configuring the Identical ASM Instance at the Recovery cluster

This procedure is required only if you are using Oracle 11g R1 with ASM. This procedure is not required for Oracle 11g R2. In this procedure, the primary cluster is referred as cluster1 and the recovery cluster is referred as cluster2.

Complete the following procedure to configure the identical ASM disk group for Oracle 11g R1 with ASM:

1.Create the Oracle admin directory at the recovery cluster, if it is not already created. In this example, run the following command from the first node in cluster1:

cd /opt/app/oracle

rcp -r admin <cluster2_node1>:$PWD

rcp -r admin <cluster2_node2>:$PWD

2.Run the following command on all nodes in the recovery cluster: chown -R oracle:oinstall /opt/app/oracle/admin

3.Copy the first ASM instance pfile and password file from the primary cluster to the first ASM instance node in the recovery cluster.

cd /opt/app/oracle/admin/+ASM/pfile rcp -p init.ora <cluster2_node1>:$PWD

cd /opt/app/oracle/product/11.1.0/db_1/dbs rcp -p orapw+ASM1 <cluster2_node1>:$PWD

The -poption retains the permissions of the file.

4.Setup the first ASM instance on the recovery cluster. In this example, run the following commands from node1 in the cluster2.

cd /opt/app/oracle/product/11.1.0/db_1/dbs

ln –s /opt/app/oracle/admin/+ASM/pfile/init.ora init+ASM1.ora chown -h oracle:oinstall init+ASM1.ora

chown oracle:oinstall orapw+ASM1

5.Copy the second ASM instance pfile and password file from cluster1 to the second ASM instance node in cluster2.

cd /opt/app/oracle/admin/+ASM/pfile rcp -p init.ora <cluster2_node1>:$PWD

cd /opt/app/oracle/product/11.1.0/db_1/dbs rcp -p orapw+ASM1 <cluster2_node1>:$PWD

The -poption retains the permissions of the file.

6.Setup the second ASM instance on the recovery cluster. In this example, run the following commands from node2 of cluster2:

cd /opt/app/oracle/product/11.1.0/db_1/dbs

Configuring Oracle RAC Database with ASM in a Site Aware Disaster Tolerant Architecture 147