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

Table 6 Variables or Parameters in haoracle.conf file (continued)
DescriptionParameter Name
NOTE: If the Oracle database package is dependent on the SGeRAC
clusterware multi-node 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 README file.
If the MAINTENANCE_FLAG attribute of the SGeRAC OC MNP is set to yes,
then this parameter must also be set to yes in the Oracle database package.
The time interval (in seconds) the script waits between checks to ensure that the
Oracle instance is running. Default is 30 seconds. This parameter must be set
in the ASM and database instance packages.
MONITOR_INTERVAL
The amount of time, in seconds, the script waits during package halt for the
Oracle database shutdown to complete before removing the Oracle processes
TIME_OUT
defined in MONITOR_PROCESSES. The TIME_OUT variable is used to protect
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. This parameter must be set for the ASM and database instance
packages.
This is used to mention if the Oracle or ASM administrator's shell should be
invoked as a new shell or as a sub-shell that inherits the variables set in the
PARENT_ENVIRONMENT
parent shell. This can be set to either 'yes' or 'no' only. Set to 'yes' if the Oracle
or ASM administrator's shell should be invoked as a sub-shell. Set to 'no' if the
Oracle or ASM administrator's shell should be invoked as a new shell. If set to
'no', the Oracle or ASM administrator's .profile file is executed and the variables
set in this .profile file are available to the new shell. This parameter can be set
in the ASM and database instance package.
This parameter indicates whether 'shutdown abort' must be executed before
the startup of the Oracle or ASM instance. 'shutdown abort' ensures the cleanup
CLEANUP_BEFORE_STARTUP
of uncleared shared memory or semaphores. This parameter can be set to only
yes or no. Default value is no. This parameter can be set in the ASM and
database instance package.
This parameter is used to specify the instance shutdown mode only when a
shutdown is initiated by the user and not due to a failure of a service. this
USER_SHUTDOWN_MODE
parameter can take values "abort" or "immediate" only. If "abort" is specified,
the instance is shutdown using the abort option. If "immediate" is specified,
the instance is shutdown using the immediate option. The default value is
"abort". This parameter can be set in the ASM and database instance package.
When ASM is being used, this parameter is used to specify if the ASM
foreground processes of the form Oracle <ASM_SID> having file descriptors
KILL_ASM_FOREGROUNDS
open on the dismounted disk group volumes should be killed during database
package halt. The Oracle scripts will wait for a timeout of 12 seconds before
terminating the foreground processes that continue to have file descriptors open
on the dismounted disk group volumes. This parameter can be set to either
"yes" or "no". The default value is 'yes'. This parameter must be set only in the
case of an ASM database instance package.
This parameter should be populated only in case the Oracle database package
is dependent on the SGeRAC OC MNP package. This parameter should point
OC_TKIT_DIR
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. This parameter
can be set only using the CLI and cannot be set using the Serviceguard
Manager.
40 Using the Oracle Toolkit in an HP Serviceguard Cluster