HP Serviceguard Oracle DataGuard Toolkit User Guide, April 2011

7 Limitations/Restrictions
1. Both the primary database and the standby database cannot be part of the same Metrocluster.
Configuring standby in the same Metrocluster will make it a redundant configuration because
the primary database is already being replicated (hardware replication) between the sites of
the Metrocluster.
2. ODG toolkit 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 even though the ECMT (or SGeRAC) supports legacy style
of packaging.
3. Multiple standby database instances cannot be supported in the Continentalclusters setup
since there can be only one Recovery package and only one Data Receiver package within
the Recovery group. Other standby instances can be configured outside the Continentalcluster
environment.
4. In a Continentalclusters environment, the 'Fast Start Failover” feature of ODG Broker has to
be disabled when using this toolkit. The “Fast start failover” feature of Data Guard Broker
enables automatic failover of the primary to one of the available standbys in case of a disaster
at the primary site. This may lead to Data Integrity issues when the toolkit attempts to failover
the primary to a different standby. Hence, it is recommended to disable “Fast Start Failover”
in Continentalclusters environment where role transitions are supported.
5. If the CRS package goes into maintenance mode, then SGeRAC DB stops monitoring the
database. But Data Guard toolkit does not go into maintenance mode automatically. The user
has to manually put it in maintenance mode.
6. Always Set the attribute START_MODE in ECMT Oracle/SGeRAC toolkit to “mount” when
using with ODG toolkit.
7. The toolkit does not perform role transitions. The role transitions must be manually performed,
if needed. When the Primary cluster goes down, the toolkit supports automatic role transitions
only in Continentalclusters environment (Both Single Instance and RAC environments)
8. Always set the attribute “START_STANDBY_AS_PRIMARY” to “yes” in case of a recovery
package of Continentalclusters environment.
9. The toolkit displays a warning message during package validation (In package apply
(cmapplyconf -P) and package check (cmacheckconf -P)) when the parameter
“START_STANNDBY_AS_PRIMARY” is set to "yes" , stating that the parameter has to be used
only in the Recovery package of the Continentalclusters environment. The toolkit thus alerts
the user to change its value to "no" if it is not a recovery package.
10. To enable Active Data Guard, the user needs an optional license from Oracle. Therefore, this
toolkit parameter should not be set to "yes" without the license.
11. ODG Broker is not supported in single instance SG environment.
12. 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).
13. 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.
36 Limitations/Restrictions