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

• When using the ODG Broker toolkit in Continentalclusters environment, the “Fast Start Failover”
feature of ODG Broker must be disabled. In case of a disaster at the primary site, the “Fast
start failover” feature of ODG Broker enables automatic failover of the primary database to
an available standby database. This may lead to Data Integrity issues when the toolkit attempts
to failover the primary to a different standby. Hence, HP recommends that you disable “Fast
Start Failover” in Continentalclusters environment where role transitions are supported.
• If the CRS package goes into maintenance mode, SGeRAC DB stops monitoring the database.
You must manually put the Data Guard toolkit into the maintenance mode because it does not
go into this mode automatically.
• Always set the attribute START_MODE in ECMT Oracle/SGeRAC toolkit to [mount] when you
use it with ODG toolkit.
• It does not perform role transitions. if required, the role transitions must be manually performed.
When the Primary cluster goes down, the toolkit supports automatic role transitions only in
Continentalclusters environment (Both Single Instance and RAC environments).
• For a recovery package of Continentalclusters environment, set the attribute
START_STANDBY_AS_PRIMARY to [yes].
• The toolkit displays a warning message during package validation (in package apply
cmapplyconf -p and package check cmacheckconf -p) when the parameter
START_STANDBY_AS_PRIMARY is set to yes. The message suggests that the parameter
must be used only in the recovery package of the Continentalclusters environment. Therefore,
the toolkit alerts you to change its value to [no] if it is not a recovery package.
• To enable Active Data Guard, the user needs an optional license from Oracle. Therefore, this
toolkit parameter must not be set to [yes] without the license.
• ODG Broker is not supported in single instance SG environment.
• If the attribute MONITOR_DG_BROKER is set to [yes], the toolkit does not monitor the mrp (lsp)
process on the physical standby database (logical standby database).
• Broker configuration should not be enabled when the parameter MONITOR_DG_BROKER is
set to [no]. If enabled, the toolkit fails the package startup to avoid issues.
Limitations 33