HP Serviceguard Toolkits for Database Replication Solutions User Guide, March 2012

database versions on all package nodes of the cluster. If there are any inconsistencies, cluster
verification logs appropriate warning messages. It does not lead to a package validation failure
during package apply or package check.
In a single-instance environment, consider a two-node cluster, where both nodes have Serviceguard
A.11.20, ECMT B.06.00 and same Oracle database versions but different ODG toolkit versions.
Use cmcheckconf to check package configuration using the node1# cmcheckconf -P
pkg.conf command:
On node2, validation of package dataguard succeeded with:
The toolkit configuration file in the toolkit configuration directory is backed up and a new file is
created when the package configuration is applied.
On node1, validation of package dataguard succeeded with:
WARNING: ODG toolkit version on all package nodes does not match.
Check syslog for more details.
cmcheckconf: Verification completed with no errors found.
Use the cmapplyconf command to apply the configuration.
Troubleshooting
This section explains some of the problem scenarios that you may encounter while working with
the ODG toolkit in an HP Serviceguard Cluster.
Recommended ActionPossible CauseProblem Scenario
Check if the primary database is up
and running and the Data Guard state
This message is logged when the
standby database is unable to connect
If the package log for the standby
database contains an error message:
RFS process not found.
Please check the network
connection.
is healthy. Also check if the connection
between the primary database and the
standby database is good. If
ALERT_MAIL_ID package attribute is
to the primary database. This could
either be because the primary
database is down, or the connection
between the primary database and
the standby database is lost.
set, then a mail is sent to the mail ID
when this problem scenario occurs.
If the Data Guard Broker is enabled for
the RAC database, the toolkit package
This message is displayed only in Data
Guard RAC configurations. This
If the RAC Data Guard package for
RAC database fails to start and logs
attribute MONITOR_DG_BROKER mustmessage is logged when the package
attribute MONITOR_DG_BROKER is set
the following message in the package
log file:
Data Guard Broker configuration should
not be enabled when MONITOR_DG_BROKER
be set to yes. Otherwise, the package
will not start.
to no and Data Guard Broker is
enabled for the database.
parameter in the Package Configuration
File is set to no.
Limitations
The ODG toolkit has the following limitations:
• Both the primary database and the standby database cannot be part of the same Metrocluster.
If standby is configured in the same Metrocluster it becomes a redundant configuration because
the primary database is already being replicated (hardware replication) between the sites of
the Metrocluster.
• It does not support legacy style configuration. Hence, the combinational package of ODG
toolkit module and ECMT Oracle toolkit Module (or SGeRAC toolkit database Module) cannot
be packaged in legacy style although the ECMT (or SGeRAC) supports legacy style of
packaging.
• Multiple standby database instances cannot be supported in the Continentalclusters setup
because only one recovery package and only one Data Receiver package can exist within
the recovery group. Other standby instances can be configured outside the Continentalclusters
environment.
32 Serviceguard toolkit for Oracle Data Guard