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

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 will put the package in toolkit maintenance mode.
Serviceguard A.11.19 release has a new feature which allows individual components
of the package to be maintained while the package is still up. This feature is called
Package Maintenance mode and is available only for modular packages. For more
information 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), then the Oracle database package will automatically go 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. More details about how to put the SGeRAC
OC MNP package in toolkit maintenance mode can be found in the 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 in case where Oracle database packages 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) will wait 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 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. If
HALT_SCRIPT_TIMEOUT is not defined then, it is the sum of all the
SERVICE_HALT_TIMEOUT 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 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 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 cmapplyconfcommand. In case
of legacy packages, this attribute must be populated manually in the haoracle.conf
file. This parameter can be set only using the CLI and cannot be set using the
Serviceguard Manager.
Support For Oracle Database without ASM 15