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

SITE_NAME san_jose
NODE STATUS STATE
SJC_1 up running
SJC_2 up running
MULTI_NODE_PACKAGES
PACKAGE STATUS STATE AUTO_RUN SYSTEM
SG-CFS-pkg up running enabled yes
sfo_crs_dg up running enabled no
sfo_crs_mp up running enabled no
sfo_crs up running enabled no
sjc_crs_dg up running enabled no
sjc_crs_mp up running enabled no
sjc_crs up running enabled no
sfo_hrdb_dg down halted enabled no
sfo_hrdb_mp down halted enabled no
sjc_hrdb_dg down halted enabled no
sjc_hrdb_mp down halted enabled no
sfo_flash_dg down halted enabled no
sfo_flash_mp down halted enabled no
sjc_flash_dg down halted enabled no
sjc_flash_mp down halted enabled no
sfo_hrdb down halted disabled no
sjc_hrdb down halted disabled no
UNOWNED_PACKAGES
PACKAGE STATUS STATE AUTO_RUN NODE
hrdb_sc down halted disabled unowned
2. Enable all nodes in the Metrocluster for the Site Controller Package.
# cmmodpkg –e –n SFO_1 –n SFO_2 -n SJC_1 –n SJC_2 hrdb_sc
3. Start the Site Controller Package.
# cmmodpkg -e hrdb_sc
The Site Controller Package and the RAC stack starts up on local site (San Francisco).
4. Check the Site Controller Package log file to ensure clean startup.
Configuring client access for Oracle database 10gR2 RAC
In Oracle database 10gR2 RAC, the Oracle Clusterware configuration provides Virtual IP addresses
(VIPs) through which database clients external to the cluster connect to the database. Oracle listeners
gather information about service availability on the RAC servers and assist in making client
connections to the RAC instances. In addition, they provide failure notifications and load advisories
to clients, therefore, enable fast failover of client connections and client-side load-balancing. These
capabilities are facilitated by an Oracle 10g feature called Fast Application Notification (FAN).
For more information on Fast Application Notification, see the following documents:
http://www.oracle.com/technology/products/database/clustering/pdf/twpracwkldmgmt.pdf
http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10gR2_ClientFailoverBestPractices.pdf
FAN capabilities can be accessed by the client application using the FAN API directly or by using
FAN-integrated clients provided by Oracle.
The Metrocluster RAC configuration uses two Oracle sub-clusters in a single SGeRAC cluster. At
any time, a given database is accessed through only one of the Oracle sub-clusters. It is referred
to as the active sub-cluster for the database. The client connectivity features mentioned above
related to fast failover and load balancing are available from the active sub-cluster. When the
database fails over to the other sub-cluster, the same features are available from that sub-cluster.
However, the client connections must be made to the VIPs configured in that Oracle sub-cluster.
There are several factors that limit the speed of client reconnection when the database fails over
across sub-clusters. When a database fails over, it does the following:
Configuring oracle RAC database in a SADTA 117