Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA A.05.01

If using SLVM, create appropriate SLVM volume groups with required raw volumes over
the replicated disks.
b. Set up file systems for RAC database flash recovery.
If you have SLVM, CVM, or CFS configured in your environment, see the following
documents available at http://www.hp.com/go/hpux-serviceguard-docs->HP
Serviceguard Extension for RAC:
• Architecture Considerations and Best Practices for Architecting an Oracle 10g R2
RAC Solution with Serviceguard and SGeRAC
• Using Serviceguard Extension for RAC
c. Create the RAC database using Oracle DBCA.
d. Configure and test RAC MNP stack at the local site.
e. Halt the RAC database.
11. Create the identical RAC database at the remote site.
a. Configure the replica RAC database.
b. Configure the RAC MNP at the remote site.
c. Halt the RAC database at the remote site.
12. Configure the Site Controller Package.
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 with the following sample configuration.
Sample configuration
To explain the configuration procedures for SADTA, the subsequent sections describe the procedure
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 A (page 77) to document key information that will be required during the configuration.
A sample configuration is used in the subsequent sections to describe the procedure to configure
Metrocluster for RAC with Oracle Database 10gR2 RAC. In this sample configuration, the following
names 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 cross-subnet
environment and the two sites are defined in the configuration file as follows:
SITE_NAME san_francisco
SITE_NAME san_jose
The RAC database is created on a shared disk in an P6000/EVA disk array, which is synchronously
replicated as part of a single replication disk group, hrdb_devgroup. The configuration uses the
Configuring oracle RAC database in a SADTA 101