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

Table 2 Lists the attributes that you can edit (continued)
ExampleDescriptionAttribute Name
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.
yesIf ASM is being used, this parameter
specifies whether any ASM
KILL_ASM_FOREGROUNDS
foreground processes having file
descriptors open on the dismounted
disk group volumes must be killed
or not.
You can set this parameter to yes
or no. The default value is yes.
If this parameter is set to yes, ASM
foreground processes of the form
oracle<ASM_SID> having file
descriptors open will be killed.
If this parameter is set to no, and if
the ASM foreground processes have
file descriptors open, it leads to
package halt and hence, fails the
package failover.
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 should 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
14 Using HP Serviceguard toolkit for Oracle