Building Disaster Recovery Serviceguard Solutions Using Metrocluster with EMC SRDF

3. Install and configure Oracle Clusterware.
4. Install Oracle Real Application Clusters (RAC) software.
5. Create the RAC database with ASM:
a. Configure ASM disk group.
b. Configure SGeRAC Toolkit Packages for the ASM disk group.
c. Create the RAC database using the Oracle Database Configuration Assistant.
d. Configure and test the RAC MNP stack at the source disk site.
e. Halt the RAC database at the source disk site.
6. Configure the identical ASM disk group at the remote site.
This step is required only for Oracle 11g R1.
7. Setup the identical RAC database at the remote site.
8. Configure the Site Controller Package.
9. Configure the Site Safety Latch dependencies.
10. Start the Disaster Tolerant RAC Database in the Metrocluster.
The subsequent sections elaborate on every of these steps.
Setting up replication
The procedure for setting up replication is identical to the procedure for setting up replication to
configure Oracle RAC with SADTA.
Configuring Metrocluster with sites
The procedure for configuring Metrocluster with sites for Oracle RAC database with ASM is identical
to the procedure for configuring Oracle RAC with SADTA.
Installing and configuring Oracle clusterware
After setting up replication in your environment and configuring Metrocluster, you must install
Oracle Clusterware. Use the Oracle Universal Installer to install and configure the Oracle
Clusterware. As SADTA requires two Oracle Clusterware sub-clusters, one at every site, you must
install and configure Oracle Clusterware twice in the Serviceguard cluster. When you install Oracle
Clusterware at a site, the sub-cluster installation is confined to a site and the Clusterware storage
is not replicated. As a result, Oracle Clusterware must be installed on a local file system at every
node in the site. The Oracle Cluster Registry (OCR) and Voting disks must be shared only among
the nodes in the site.
For every Oracle RAC 11g R2 clusterware installation, one Single Client Access Name (SCAN),
which must resolve to one public IP, is required. SCAN allows clients to use one name in the
connection strings to connect to every sub cluster as whole. A client connection request can be
handled by any CRS sub cluster node. Because in a Metrocluster, there are two sites and two CRS
sub clusters, you must configure a separate SCAN for every CRS sub cluster.
To configure the storage device for installing Oracle clusterware, see the latest edition of Using
Serviceguard Extension for RAC available at http://www.hp.com/go/hpux-serviceguard-docs.
Configuring SGeRAC toolkit packages for every Oracle clusterware sub-cluster
To configure SADTA, the Clusterware daemons must be managed through HP Serviceguard. As a
result, the clusterware sub-cluster at the site must be packaged using the HP Serviceguard extension
for RAC toolkit. This configuration must be done at both sites in the Metrocluster. Also, ensure that
the package service is configured to monitor the Oracle Clusterware. For information about
configuring the Clusterware packages, see the see the HP SGeRAC Toolkit README.
SGeRAC toolkit packages can be created using the Package Easy Deployment feature available
in Serviceguard Manager version B.03.10. For more details, see Using Easy Deployment in
Serviceguard and Metrocluster Environments on HP-UX 11i v3 available at http://www.hp.com/
go/hpux-serviceguard-docs —> HP Serviceguard.
Configuring Oracle RAC database with ASM in a SADTA 121