HP Serviceguard Toolkit for Oracle on Linux User Guide (May 2013)

Table 3 Lists the attributes that you can edit (continued)
ExampleDescriptionAttribute
Oracle looks out for the
oracle.debug file in the Oracle
package directory.
If the file exists and if the
maintenance feature is enabled, then
monitoring is paused, the ASM or
the database instance might be
brought down for maintenance, and
package does not fail over to the
adoptive node even though the
instance is not running.
After the maintenance work, ensure
that the instance is running. Then
delete the file oracle.debug in
the package directory. This enables
the toolkit to continue monitoring the
database server application or the
ASM instance. The default value is
yes.
NOTE: If the Maintenance flag is
set to no, then the maintenance
feature is not available which means
the toolkit cannot be brought into
maintenance mode.
30The time interval, in seconds, this
script waits between checks to
MONITOR_INTERVAL
ensure that Oracle 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.
noThis parameter is used to mention if
the Oracle or ASM user's shell must
PARENT_ENVIRONMENT
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. The default value is 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
20 Using HP Serviceguard toolkit for Oracle