Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy

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 68) 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, 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 and Site B.
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 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 san_francisco
SITE_NAME san_jose
The RAC database is created on a shared disk in a 3PAR disk array, which is synchronously
replicated as part of a single replication disk group, hrdb_devgroup. The configuration uses the
CFS file system as the host for database storage management. The underlying Serviceguard cluster
is configured with the site, therefore, there are two CFS sub-clusters; one at the San Francisco site
with membership from SFO_1 and SFO_2 nodes and the other at the San Jose site with membership
from SJC_1 and SJC_2 nodes.
Figure 12 Sample configuration
Configuring Oracle RAC database in a SADTA 77