7.Configure the Site Controller Package and the Site Safety Latch.

8.Configure client access for Oracle Database 10gR2 RAC.

The subsequent sections discuss each step in detail.

Setting up Replication

The RAC database data files and the flash recovery area should be replicated between the site disk arrays. The underlying disks must be configured for replication. The replication mechanisms differ depending on the type of arrays in your environment. For more information on configuring replication for the arrays in your environment, see the respective chapters of this manual.

Configuring Metrocluster with Sites

To configure SADTA, a Serviceguard cluster must be created that comprises nodes from both sites. In this example, a Serviceguard cluster is created using nodes SFO_1, SFO_2, SJC_1, and SJC_2.

This example also describes a cross-subnet Serviceguard cluster. There are rules and guidelines to configure a cross-subnet cluster. For more information on configuring cross-subnet Serviceguard clusters, see Chapter 1 (page 23).

To configure Metrocluster, complete the following steps:

1.Create a Serviceguard cluster with the sites configured.

2.Configure the Cluster File System Multi-node Package (SMNP).

The following sections describe each of these steps in detail.

Creating a Serviceguard Cluster with Sites Configured

Complete the following steps to create a Serviceguard cluster with sites configured:

1.Run the following command to create a cluster configuration file from any node: cmquerycl

In this example, the command is:

cmquerycl -v -C /etc/cmcluster/dbcluster.config -n SFO_1 -n SFO_2\ -n SJC_1 -n SJC_2 -w full -q quorum.abc.com

where quorum.abc.com is the host name of the Quorum Server.

2.Edit the /etc/cmcluster/dbcluster.config file to specify the site configuration. Following is a sample of the configuration file:

SITE_NAME san_francisco SITE_NAME san_jose

NODE_NAME

sfo_1

SITE

san_francisco

NETWORK_INTERFACE

lan2 #SG HB 1

HEARTBEAT_IP

192.1.3.1

NETWORK_INTERFACE

lan3 #SG HB 2

HEARTBEAT_IP

192.1.5.1

NETWORK_INTERFACE

lan4 #SFO_CRS CSS HB

STATIONARY_IP

192.1.7.1

NETWORK_INTERFACE

lan5 #SFO_CRS CSS HB standby

NETWORK_INTERFACE

lan1 # SFO client access

STATIONARY_IP

16.89.140.201

NETWORK_INTERFACE

lan6 # SFO client access standby

NODE_NAME

sfo_2

SITE

san_francisco

NETWORK_INTERFACE

lan2 #SG HB 1

HEARTBEAT_IP

192.1.3.2

NETWORK_INTERFACE

lan3 #SG HB 2

HEARTBEAT_IP

192.1.5.2

Configuring Oracle RAC Database in a Site Aware Disaster Tolerant Architecture 367