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

When the primary cluster fails, run "cmrecovercl" command on the recovery
cluster to bring up the
recovery package.
I. Using Serviceguard Toolkit for Oracle Data Guard in Metrocluster and
Extended Distance Cluster environments:
The Primary database can be configured inside a Metrocluster or an
Extended Distance Cluster. The standby
database can be configured outside the Metrocluster/Extended Distance
Cluster as a standalone database or
as part of a Serviceguard cluster.
For information about setting up Metrocluster, see the document
"Designing Disaster
Recovery HA Clusters Using Metrocluster and Continentalclusters Manual"
available at
http://www.hp.com/go/hpux-serviceguard-docs
J. Verification of the setup:
This section provides the guidelines to verify if the Oracle Data Guard
package has been configured
properly or not.
The following steps helps the user to troubleshoot the possible causes
for the package failure.
1. Verify Oracle Data Guard setup:
To verify a Data Guard configuration, check if the standby database is
able to receive the redo logs.
Also check if the RFS process is running on the standby database by
querying the table "V$MANAGED_STANDBY".
If the standby site is not receiving the logs, obtain information about
the archiving status of the
primary database by querying the V$ARCHIVE_DEST view. Check especially
for error messages. For example, enter:
SQL> SELECT dest_id "ID",
2> status "DB_status",
3> destination "Archive_dest",
4> error "Error"
5> FROM v$archive_dest;
ID DB_status Archive_dest Error
-- --------- ------------------------------
--------------------------------------
1 VALID /vobs/oracle/work/arc_dest/arc
2 ERROR standby1 ORA-16012: Archivelog standby database
identifier mismatch
3 INACTIVE
4 INACTIVE
5 INACTIVE