Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA A.05.01

storage mechanism for the database and select the Use Oracle-managed files option to store
database files and provide the ASM DG that you created earlier.
Configuring and testing the RAC MNP stack at the Source Disk Site
To configure Oracle RAC Database with ASM in SADTA, the RAC database must be packaged
in Serviceguard MNP packages in both sites. Also, automatic startup of RAC database instances
and services at Clusterware startup must be disabled. For more information on disabling automatic
startup of RAC databases, see the How To Remove CRS Auto Start and Restart for a RAC Instance
document available at the Oracle documentation site. For information on configuring the RAC
database in the MNP packages, see the HP SGeRAC Toolkit README.
Configure the RAC MNP package to have dependency on the site’s Clusterware sub-cluster MNP
package and the site’s ASM disk group MNP package.
Ensure that in RAC MNP package, the service is configured to monitor the Oracle RAC database.
Before halting the RAC MNP stack, test the configuration to ensure that the packages are configured
appropriately and can be started.
Halting the RAC database on the Source Disk Site
After creating the RAC database on the source disk site, you must halt it to replicate it on the target
disk site. If you are using 11g R2 RAC, you must change the remote_listener for the database
before halting the RAC database MNP stack as explained in step 1.
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 each 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 before 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.
Before setting up an identical RAC database at the target disk site, make the target disk in the
Read/Write mode. Using HP P6000 Command View failover to the destination DR Group to make
it Read/Write. After preparing the replicated disk at the target disk site, a storage device must be
configured. For more information on configuring a storage device, see “Setting up replication”
(page 35).
122 Configuring Oracle RAC in SADTA