HP Enterprise Cluster Master Toolkit User Guide (5900-2131, December 2011)

Table 3 Variable or Parameter Name in haoracle.conf file (continued)
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
TIME_OUT
used as protection 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.
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 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
PARENT_ENVIRONMENT
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/ASM instance. 'shutdown abort' ensures the cleanup of uncleared
CLEANUP_BEFORE_STARTUP
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 a 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 e-mail address for sending alerts.ALERT_MAIL_ID
This parameter must be populated only in case of Oracle database packages being
created using ECMT Oracle toolkit provided that SGeRAC packages are also running
OC_TKIT_DIR
in the same cluster and Oracle database packages being dependent on SGeRAC OC
MNP package. This parameter must point to the working directory of the SGeRAC
OC MNP. In case of modular packages, the value for this parameter is automatically
populated when the package is created using the cmapplyconf command. In case of
legacy packages, this attribute must be populated manually in the haoracle.conf file.
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 above 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)
analogous to the package directory in the legacy method of packaging. The
ADF is used to generate a package ASCII template file.
This script is called by the Master Control Script and acts as an interface
between the Master Control Script and the Toolkit interface script
Module Script (tkit_module.sh)
(toolkit.sh). It is also responsible for calling the Toolkit Configuration File
Generator Script (described below).
This script is called by the Module Script when the package configuration is
applied using cmapplyconf to generate the user configuration file in the
package directory (TKIT_DIR).
Toolkit Configuration File Generator
Script (tkit_gen.sh)
16 Using the Oracle Toolkit in an HP Serviceguard Cluster