Using the Serviceguard Toolkit for Oracle Data Guard in an HP Serviceguard Cluster B.01.00, September 2010

6. Allow monitoring scripts to continue normally as shown below:
$ rm -f /etc/cmcluster/pkg/dgpkg/dataguard.debug
The message "Starting Oracle Data Guard monitoring again after
maintenance"
appears in the Serviceguard Package Control script log.
7. Enable the package failover
$ cmmodpkg -e dgpkg
Note: If a package failure occurs during maintenance operations, the
package does not
automatically fail over to an adoptive node. You must manually start the
package on the
adoptive node. For more information on manually starting the package on
an adoptive node,
see the "Managing HP Serviceguard" guide available at:
http://www.hp.com/go/hpux-serviceguard-docs
H. Using Serviceguard Toolkit for Oracle Data Guard in
Continentalclusters environment:
A Continental cluster provides an alternative disaster tolerant solution
in which two clusters
are geographically dispersed.
For information about setting up Continentalclusters, see the document
"Designing Disaster
Recovery HA Clusters Using Metrocluster and Continentalclusters Manual"
available at
http://www.hp.com/go/hpux-serviceguard-docs
In Continentalclusters environment the user needs to configure a recovery
group which
consists of
1. Primary package: This package has to be created for the primary
database on the primary cluster.
Create a combinational package for the primary database with ECMT Oracle
toolkit and the ODG toolkit.
2. Data receiver package: This package has to created for the standby
database on the recovery cluster.
Create a combinational package for the standby darabase using ECMT Oracle
toolkit and the ODG toolkit.
3. Recovery package: This package has to be created for the standby
database on the recovery cluster.
Create a combinational package for the standby database using ECMT Oracle
toolkit and the ODG toolkit.
Note that the package attribute "START_STANDBY_AS_PRIMARY" has to be set
to "yes" in case of a recovey
package.