HP Serviceguard Enterprise Cluster Master Toolkit User Guide (5900-2145, April 2013)

Table 3 Variable or Parameter Name in haoracle.conf file (continued)
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.
IfHALT_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.
This parameter is used to mention whether 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
PARENT_ENVIRONMENT
can be set to only yes or 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.
This parameter indicates whether 'shutdown abort' needs to be executed before the
startup of the Oracle or ASM instance. 'shutdown abort' ensures the cleanup of
CLEANUP_BEFORE_STARTUP
uncleared shared memory or semaphores. This parameter can be set to only yes or
no. Default value is 'no'.
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 service. This parameter can take
USER_SHUTDOWN_MODE
values "abort" or "immediate" only. If "abort" is specified, the database is shutdown
using the abort option. If "immediate" is specified, the database is shutdown using
the immediate option.
This parameter is used to specify the email address for sending alerts.ALERT_MAIL_ID
This parameter is used to set the time interval to wait in case of ORA errors during
database hang monitor. If there is any ORA error during hang monitor, the toolkit
RETRY_INTERVAL_ORA_ERROR
retries three times with a time interval of RETRY_INTERVAL_ORA_ERROR seconds. If
all the consecutive retry fails, then it is considered as failure. This avoids unnecessary
failover in case of temporary ORA errors. The implication is that it delays the detection
of db hang by 3 * RETRY_INTERVAL_ORA_ERROR seconds in case of actual ORA
errors.
nl
By default, RETRY_INTERVAL_ORA_ERROR is set to zero. When this parameter is set
to zero, there is no delay in database hang detection since toolkit will not retry.
This parameter is used to withdraw backup mode from the Oracle database. The valid
values for this parameter are yes or no. The default value is no. This means, if the
DISABLE_BACKUP_MODE
database is in backup mode, after failover or restart, the Oracle toolkit package fails
to start. You must manually bring the database out of the backup mode and then start
the package. When the value of DISABLE_BACKUP_MODE is set to yes and the
database is in backup mode, after failover or restart, the Oracle toolkit package alters
the database to remove the backup mode, and starts the database. This task is
performed only if START_MODE is set to open.
For modular packages, there is an Attribute Definition File (ADF) - oracle.1, a Toolkit Module Script
(tkit_module.sh), and a Toolkit Configuration File Generator Script (tkit_gen.sh) that work with
the six scripts mentioned in Table 3 for legacy packages, to integrate Oracle with the Serviceguard
Master Control Script.
NOTE: The following three scripts are used only during the modular method of packaging.
Table 4 Modular Package Scripts
DescriptionScript Name
For every parameter in the legacy toolkit user configuration file, there is an
attribute in the ADF. It also has an additional attribute TKIT_DIR which is
Attribute Definition File (oracle.1)
Support for Oracle Database Without ASM 17