13.Configure the Site Safety Latch dependencies.
14.Start the site aware disaster tolerant RAC database in the Metrocluster.
15.Configure client access for the RAC database.
16.Configure SGeRAC cluster interconnect subnet monitoring.
The subsequent sections explain each of these steps in detail.
Sample Configuration
To illustrate the configuration procedures for SADTA, the subsequent sections describe how to install and configure a site aware disaster tolerant Oracle Database 10gR2 RAC in a Metrocluster. The configuration procedure involves multiple steps across multiple nodes. Use the worksheet in Appendix G (page 506) to document key information that will be required during the configuration.
A sample configuration is used in the subsequent sections to elaborate on the procedure to configure Metrocluster for RAC with Oracle Database 10gR2 RAC. In this sample configuration, following are the names that are used:
•hrdb
This is the Oracle Database 10gR2 RAC that is configured with two database instances, which are configured using SADTA in a Metrocluster environment.
•dbcluster
The Metrocluster that spans two cities, San Francisco and San Jose.
•SFO_1 and SFO_2
The two nodes at the San Francisco site that are connected to a disk array that supports the SADTA feature.
•SJC_1 and SJC_2
The two nodes at the San Jose site that are connected to a disk array that supports the SADTA feature.
The disk arrays at the San Francisco and the San Jose sites have a physical replication link configured between them. The underlying Serviceguard cluster is configured in a
SITE_NAME san_francisco
SITE_NAME san_jose
The RAC database is created on a shared disk in an XP disk array, which is synchronously replicated as part of a single replication disk group, hrdb_devgroup. The configuration uses the CFS file system at the host for database storage management. As the underlying Serviceguard cluster is configured with the site, there are two CFS
364 Designing a Disaster Recovery Solution Using Site Aware Disaster Tolerant Architecture