Building Disaster Recovery Serviceguard Solutions Using Metrocluster with EMC SRDF

1. When using Oracle 11g R2 with ASM, the remote_listener for the database is set to the
<SCAN name>:<port number> by default. But, in the Metrocluster for RAC configuration, the
SCAN name is different for every site CRS subcluster. So, the remote_listener for the database
must be changed to the net service name configured in the tnsnames.ora for the database.
This task must be done prior to halting the RAC database stack on the Source Disk Site:
a. Log in as the Oracle user.
# su – oracle
b. Export the database instance on the node. In this example, hrdb1 is database instance
running on this node.
export ORACLE_SID=”hrdb1”
c. Alter the remote listener:
# sqlplus “/ as sysdba”
d. At the prompt, enter the following:
SQL> show parameter remote_listener;
SQL> alter system set remote_listener=’hrdb’;
2. Halt the RAC MNP Stack on the replication Source Disk Site node:
# cmhaltpkg <site1_rac_db_pkg> <site1_asmdg_pkg1>
Setting up identical RAC database at the target disk site
In the earlier procedures, the RAC database was created at the site with the source disk of the
replication disk group, referred as the source disk site. A RAC MNP stack was also created at that
site. Now, an identical RAC database using the target replicated disk must be configured with the
RAC MNP stack. The site to which the data is replicated is referred as Target Disk Site in this
section.
Prior to setting up an identical RAC database at the target disk site, the data replication must first
be split 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 target disk site, a storage device must be configured.
Configuring the Identical ASM Disk Group at the Target Disk Site
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 source disk site is referred as site1 and the
target disk site is referred as site2.
To configure the identical ASM disk group for Oracle 11g R1 with ASM:
1. Create the Oracle admin directory at the target disk site, if it is not already created.
In this example, run the following command from the first node in site1:
# cd /opt/app/oracle
# rcp -r admin <site2_node1>:$PWD
# rcp -r admin <site2_node2>:$PWD
2. Run the following command at the target disk site:
# chown -R oracle:oinstall /opt/app/oracle/admin
3. Copy the first ASM instance pfile and password file from the source disk site to the first
ASM instance node in the target disk site.
# cd /opt/app/oracle/admin/+ASM/pfile
# rcp -p init.ora <site2_node1>:$PWD
# cd /opt/app/oracle/product/11.1.0/db_1/dbs
# rcp -p orapw+ASM1 <site2_node1>:$PWD
Configuring Oracle RAC database with ASM in a SADTA 123