Security Solutions

available at http://www.hp.com/go/hpux-serviceguard-docs -> HP Serviceguard Extension for
RAC -> Using Serviceguard Extension for RAC.
Configuring SGeRAC toolkit packages for the ASM disk group in the primary cluster
To configure Oracle RAC database with ASM in Continentalclusters using SADTA, the ASM disk
group must be packaged in Serviceguard MNP packages in both the clusters. Configure ASM Disk
group MNP package dependency on the Clusterware MNP package on both the clusters.
Creating the Oracle RAC database in the primary cluster
After setting up the ASM disk group for the RAC database data files, you must create the RAC
database. You can use the Oracle Database Configuration Assistant (DBCA) to create the RAC
database. After you login to the DBCA, select the Automatic Storage Management option as the
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 in the primary cluster
To configure Oracle RAC Database with ASM in SADTA, the RAC database must be packaged
in Serviceguard MNP packages in both clusters. 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 Using Serviceguard Extension for RAC available at http://
www.hp.com/go/hpux-serviceguard-docs -> HP Serviceguard Extension for RAC -> Using
Serviceguard Extension for RAC.
Configure the RAC MNP package to have dependency on the Clusterware MNP package and
ASM disk group MNP package. This step completes the configuration of the RAC MNP stack in
the primary cluster. 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 in the primary cluster
After creating the RAC database in the primary cluster, you must halt it to replicate it on the recovery
cluster. 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 step1.
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 Continentalclusters configuration, the
SCAN name is different for every cluster CRS. 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 in the primary cluster:
a. Log in as the Oracle user.
# su – oracle
b. Export the database instance on the node. In this example, hrdb1 is the 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 primary cluster node:
# cmhaltpkg <cluster1_rac_db_pkg> <cluster1_asmdg_pkg1>
Creating the RAC database with ASM in the primary cluster 139