User's Manual

Table 6 Variables or Parameters in haoracle.conf file (continued)
DescriptionParameter Name
This variable will enable or disable toolkit maintenance mode for the Oracle
database package and ASM MNP. By default, this is set to "yes". To disable
this feature, MAINTENANCE_FLAG must be set to "no". When Oracle Database
or ASM must be maintained, then a file "<package directory >/Oracle.debug”
must be created. During this maintenance period, the Database or ASM
instance's process monitoring is paused. Even if the instance is brought down,
its package will not be failed over to the standby node.
To continue monitoring and to exit from the maintenance mode, you must
remove the Oracle.debug file. It is user's responsibility to ensure that the
instance is properly running after the maintenance phase. This parameter can
be set in the ASM and database instance package.
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.
MAINTENANCE_FLAG
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
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.
TIME_OUT
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 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.
PARENT_ENVIRONMENT
This parameter indicates whether 'shutdown abort' must be executed before
the startup of the Oracle or ASM instance. 'shutdown abort' ensures the cleanup
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.
CLEANUP_BEFORE_STARTUP
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
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.
USER_SHUTDOWN_MODE
Setting Up the Toolkit 39