HP Serviceguard Linux Oracle-Toolkit-A.05.01.00 User Guide (696983-001, June 2012)

ExampleDescriptionAttribute
After the maintenance work,
ensure that the instance is running.
Then delete the oracle.debug
file in the package directory. This
enables toolkit to continue
monitoring the database server
application or the ASM instance.
NOTE: If Maintenance flag is set
to no, then the maintenance
feature is not available and toolkit
cannot be brought into
maintenance mode.
30The time interval, in seconds, this
script waits between checks to
MONITOR_INTERVAL
ensure that ASM instance is
running. The default value is 30
seconds.
30The time period, in seconds, this
toolkit waits for a completion of a
TIME_OUT
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.
The TIME_OUT variable has no
effect on package failover times.
The default value is 30 seconds.
yesThis parameter is used to mention
if the Oracle or ASM user's shell
PARENT_ENVIRONMENT
must be invoked as a new shell or
as a subshell that inherits the
variables set in the parent shell.
You can set this parameter to yes
or no. Set this parameter to yes
if the Oracle or ASM user's shell
must be invoked as a subshell.
Set to no if the Oracle or ASM
user's shell must be invoked as a
new shell. If set to no, the Oracle
or ASM user's .profile file is
executed and the variables set in
this file are available to the new
shell.
noThis parameter indicates whether
shutdown abort must be executed
CLEANUP_BEFORE_STARTUP
before the startup of the Oracle or
ASM instance.
You can set this parameter to yes
or no. The default value is no.
Configuring legacy and modular Oracle database toolkit packages 33