Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access for P9000 and XP A.11.00

Configuring the Site Safety Latch dependencies
After the Site Controller Package configuration is applied, the corresponding Site Safety Latch is
also configured automatically in the cluster. This section describes the procedure to configure the
Site Safety Latch dependencies.
To configure the Site Safety Latch dependencies:
1. Add the EMS resource details in ASM DG package configuration file.
RESOURCE_NAME /dts/mcsc/hrdb_sc
RESOURCE_POLLING_INTERVAL 120
RESOURCE_UP_VALUE != DOWN
RESOURCE_START automatic
You must apply the modified ASM DG package configuration using the cmapplyconf
command.
2. Verify the Site Safety Latch resource configuration at both sites.
Run the following command to view the EMS resource details:
# cmviewcl -v –p <ASM_DG_pkg_name>
3. Configure the Site Controller Package with the RAC MNP stack packages of both sites.
site site1
critical_package <site1_RAC_DB_pkg_name>
managed_package <site1_ASM_DG_pkg_name>
site site2
critical_package <site2_RAC_DB_pkg_name>
managed_package <site2_ASM_DG_pkg_name>
NOTE: Do not add any comments after specifying the critical and managed packages.
4. Re-apply the Site Controller Package configuration.
# cmapplyconf -v -P <site_controller_configuration_file>
After applying the Site Controller Package configuration, run the cmviewcl command to view the
packages that are configured.
Starting the disaster tolerant Oracle RAC database with ASM in the Metrocluster
The procedure to start the disaster tolerant Oracle RAC database with ASM is identical to the
procedure for starting a complex workload in a Metrocluster. For more information about starting
the complex workload in the Metrocluster, see “Starting the complex workload in the Metrocluster”
(page 49).
Failure scenarios in Metrocluster for RAC
This section elaborates on the failure scenarios in Metrocluster for RAC.
This section addresses the following topics:
• “Oracle RAC database failure ” (page 217)
• “Oracle RAC database instance failure” (page 218)
• “Oracle RAC database Oracle clusterware daemon failure” (page 218)
Oracle RAC database failure
When failures such as tablespace corruption, or errors arising out of insufficient storage space
occur, the RAC database instance processes on the nodes fail. When the Oracle RAC database
instance fails at a site, the RAC MNP package instance containing it also fails. The Site Controller
Package that monitors the RAC MNP package detects that the RAC MNP has failed. The database
Failure scenarios in Metrocluster for RAC 217