HP Serviceguard Enterprise Cluster Master Toolkit User Guide, December 2012 (5900-2145)

Table 3 Variable or Parameter Name in haoracle.conf file (continued)
NOTE: Setting MAINTENANCE_FLAG to "yes" and touching the oracle.debug
file in the package directory puts the package in toolkit maintenance mode.
Serviceguard A.11.19 release has a new feature which allows the maintenance of
individual components of the package while the package is still up. This feature is
called Package Maintenance mode and is available only for modular packages. For
more information on using Package Maintenance mode, see Modular package support
in Serviceguard for Linux and ECM Toolkits available at http://www.hp.com/go/
hpux-serviceguard-docs —>HP Serviceguard Enterprise Cluster Master Toolkit.
If the Oracle database package is dependent on the SGeRAC clusterware package
(OC MNP), the Oracle database package automatically gets into toolkit maintenance
mode if the SGeRAC OC MNP is put into toolkit maintenance mode. To put the
SGeRAC OC MNP into toolkit maintenance mode, its MAINTENANCE_FLAG attribute
must be set to 'yes' and a file oc.debug must be created manually in the OC MNP
working directory on that node. For more information on how to put the SGeRAC OC
MNP package in toolkit maintenance mode, see SGeRAC toolkit user guide. If the
MAINTENANCE_FLAG attribute of the SGeRAC OC MNP is set to 'yes', this parameter
must also be set to 'yes' in the single-instance Oracle database package.
This parameter must be set only if Oracle database packages are created using ECMT
Oracle toolkit and SGeRAC packages run in the same cluster. This parameter must be
set to the Oracle Clusterware home directory.
ORA_CRS_HOME
The time interval script (in seconds) waits between checks to ensure that the Oracle
instance is running. Default value is 30 seconds.
MONITOR_INTERVAL
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 prevents 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. If HALT_SCRIPT_TIMEOUT is not defined,
it is the sum of all the SERVICE_HALT_TIMEOUT defined in the package. This variable
has no effect on the number of times a package fails over.
This 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 can be set
PARENT_ENVIRONMENT
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 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 email address for sending alerts.ALERT_MAIL_ID
This parameter is used if an Oracle database package is created using ECMT Oracle
toolkit, along with SGeRAC packages running in the same cluster and Oracle database
OC_TKIT_DIR
packages being dependent on SGeRAC OC MNP package. This parameter must point
to the working directory of the SGeRAC OC MNP. For modular packages, the value
for this parameter is automatically populated when the package is created using the
cmapplyconfcommand. For legacy packages, this attribute must be populated
manually in the haoracle.conf file. To set this parameter, you must use the CLI and
not the Service Manager.
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
16 Using the Oracle Toolkit in an HP Serviceguard Cluster