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 on starting the complex workload in the Metrocluster, see “Starting the Disaster Tolerant Complex Workload in the Metrocluster” (page 359).
Understanding Failure Scenarios in a Site Aware Disaster Tolerant Architecture
This section describes how various site failover scenarios are addressed in SADTA.
This section addresses the following topics:
•“Failure Scenarios in a Complex Workload” (page 391)
•“Failure Scenarios in Metrocluster for RAC” (page 394)
Failure Scenarios in a Complex Workload
This section elaborates on the failure scenarios that can occur when a complex workload is configured using Site Aware Disaster Tolerant Architecture.
This section addresses the following topics:
•“Node Failure and Rejoining the Cluster” (page 392)
•“Network Partitions Across Sites” (page 393)
•“Disk Array and SAN Failure” (page 393)
•“Replication Link Failure” (page 393)
•“Site Controller Package Failure” (page 393)
Site Failover
When the Site Controller Package determines that a running package configuration of a disaster tolerant complex workload has failed in the Metrocluster, or that the site hosting it has failed, it fails over to the remote site node and initiates a site failover from the remote node. The site failover starts the adoptive
The Site Controller Package monitors the active
A
The Site Controller Package determines a failure by checking if the package_halted flag is set to no for all monitored packages that are in the down state. When the monitored packages have
Understanding Failure Scenarios in a Site Aware Disaster Tolerant Architecture 391