Using the Oracle Toolkit in a HP Serviceguard Cluster README Revision: B.06.00, August 2010

MONITOR_INTERVAL: The time interval, in seconds, script
will wait between checks to ensure that
the Oracle instance is running. Default
value is 30 seconds.
TIME_OUT: The amount of time, in seconds, to wait
for the Oracle abort to complete before
killing the Oracle processes defined in
MONITOR_PROCESSES. The TIME_OUT variable
is used to protect against a worst-case
scenario where a hung instance prevents
the package halt script from completing,
therefore preventing the standby node
from starting the instance. The value of
TIME_OUT must be less than the
HALT_SCRIPT_TIMEOUT value set in the
package configuration file. If
HALT_SCRIPT_TIMEOUT is not defined then
it is the sum of all the
SERVICE_HALT_TIMEOUT's defined in the
package. This variable has no effect on
the package failover times.
PARENT_ENVIRONMENT: This is used to mention if the Oracle
user's shell should be invoked as a new
shell or as a subshell that inherits the
variables set in the parent shell. This
can be set to only yes/no. Set to yes if
the Oracle user's shell should be invoked
as a subshell. Set to no if the Oracle
user's shell should be invoked as a new
shell. If set to no, the Oracle user's
.profile file is executed and the
variables set in this .profile file are
available to the new shell.
CLEANUP_BEFORE_STARTUP: This parameter indicates whether
'shutdown abort' needs to be executed
before the startup of the Oracle/ASM
instance. 'shutdown abort' ensures the
cleanup of uncleared shared memory or
semaphores. This parameter can be set
to only yes or no. Default value is no.
USER_SHUTDOWN_MODE: This parameter is used to specify the
database shutdown mode only when a
shutdown
is initiated by the user and not due to
a failure of a service. This parameter can
take values "abort" or "immediate" only.
If "abort" is specified, the database is