Figure 26 Sample Oracle RAC Database with ASM in SADTA
The CRS daemons at the clusters must be configured as a Serviceguard package using the HP Serviceguard extension for RAC (SGeRAC) toolkit at each Serviceguard cluster. The CRS Home must be installed on a file system that is local to the cluster. The CRS voting and OCR disks must not be configured for replication.
The RAC database software must be installed at each cluster in the Continentalclusters. Create ASM disk groups at the nodes in the primary cluster and configure an identical ASM disk group at the recovery cluster. The ASM disk group (ASM DG) must be configured as a Serviceguard package using the SGeRAC toolkit at each cluster.
The ASM DG package must have dependency on the CRS package on the cluster. Two replicas of the RAC database must be configured; one at the primary cluster and the other at the recovery cluster. The database must be created at the nodes in source site of the replication and the configuration and data must be replicated to the nodes in the other site.
The RAC database (RAC DB) must be configured using the SGeRAC toolkit at each site. The RAC DB package must have dependency on the CRS package and the ASM DG packages on the cluster.
This section describes the procedures that must be followed to configure SADTA with Oracle RAC database with ASM. To explain these procedures, it is assumed that the Oracle RAC home directory is /opt/app/oracle/product/11.1.0/db_1/dbs and the database name is hrdb.
To configure SADTA with Oracle RAC database with ASM in Continentalclusters with SADTA, complete the following steps:
1.Set up replication between the primary cluster and the recovery cluster.
2.Configure a primary cluster with a single site defined in the Serviceguard cluster configuration file.
Configuring Oracle RAC Database with ASM in a Site Aware Disaster Tolerant Architecture 143