1.Create a package directory on all nodes in the site. mkdir -p /etc/cmcluster/pkg/sfo_ic

2.Create a package configuration file and control script file. Use site-specific names for the files. You must follow the legacy package creation steps.

cmmakepkg -p sfo_ic.conf cmmakepkg -s sfo_ic.cntl

3.Specify a site-specific package name in the package configuration file.

4.Specify only the nodes in the site for the node_name parameter.

5.Specify the package type as MULTI_NODE.

6.Specify the SGeRAC Cluster Interconnect as CLUSTER_INTERCONNECT_SUBNET.

7.Save and apply the package configuration file. cmapplyconf –P sfo_ic.conf

Configuring and Administration Restrictions

Following are the configuration and administration restrictions that apply to SADTA configurations for application workloads:

•Only two sites can be configured in Metrocluster configuration.

•All Serviceguard restrictions that apply to site configurations also apply to configuring Metrocluster for RAC.

•For a RAC database that is configured in Metrocluster for RAC, the redundant database configuration at each site sub-cluster must have same number of instances.

•When using VERITAS CVM, each CVM disk group must be configured with a Modular package at both sites.

Configuring Oracle RAC Database with ASM in a Site Aware Disaster Tolerant Architecture

Automatic Storage Management (ASM) is a feature in Oracle Database 10g and 11g that provides the database administrator with a simple storage management interface that is consistent across all server and storage platforms. In Metrocluster, Oracle RAC with ASM can be configured using the SADTA. Figure 62 (page 384) illustrates two Oracle RAC databases that are replicas of each other, are configured one at each cluster in Continentalclusters with SADTA. The database workload at each cluster has its own Site Controller package and Site Safety Latch. The arrows in the figure indicate the package dependencies.

Configuring Oracle RAC Database with ASM in a Site Aware Disaster Tolerant Architecture 383