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

instance may be brought down for maintenance. The
package would not be
failed over to the adoptive node even though the
instance has been
brought down for maintenance. After the maintenance
work, make sure that
the instance is brought up properly. Delete the file
dataguard.debug
the package directory. This would enable toolkit to
continue monitoring
the Database server application.
Note if Maintenance flag is set to "no" then the above
feature would
not be available and toolkit cannot be brought into
maintenance mode.
MONITOR_INTERVAL: The time interval, in seconds, this script will
wait between checks to
make sure that the Oracle instance is running. The
default value is 30
seconds.
TIME_OUT: The time for which the toolkit waits for a completion of
a normal shutdown
before initiating forceful halt of the application. The
TIME_OUT variable
is used to protect against a worst case scenario where a
hung database
or ASM instance prevents the halt script from
completing, therefore
preventing the standby node from starting the instance
TIME_OUT
variable has no effect on package failover times. The
default value is 30
seconds.
ACTIVE_STANDBY: This parameter determines whether the database instance
is an active
standby or not. The Active Data Guard Option available
with Oracle Database
11g Enterprise Edition enables you to open a physical
standby database for
read-only access. This parameter can be set to 'yes' or
'no'. The default
value is 'no'
DG_BROKER: Specify whether the Oracle Data Guard broker is to be
used or not. Oracle
Data Guard Broker management is not supported in this
release. Hence this
parameter must be set to "no". The default value is
"no".