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

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 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 A (page 154) to document key information that is 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, Site A cand Site B.
SFO_1 and SFO_2
The two nodes at the Site A site that are connected to a disk array that supports the SADTA
feature.
SJC_1 and SJC_2
The two nodes at the Site B site that are connected to a disk array that supports the SADTA
feature.
The disk arrays at the Site A and the Site B 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 Site A
SITE_NAME Site B
The RAC database is created on a shared disk in a P9000/XP disk array, which is synchronously
replicated as part of a single replication disk group, hrdb_devgroup. The configuration uses the
192 Configuring Oracle RAC in SADTA