Using Serviceguard Extension for RAC, 10th Edition, April 2011

created manually on that node. During this maintenance period the Oracle
Clusterware process checking is paused. Even if Oracle Clusterware is
brought down on the local node, the OC MNP on that node will not be halted.
When the OC MNP is in maintenance mode and the RAC MNP maintenance mode is
enabled, the corresponding RAC MNP on the same node will be in maintenance
mode as well regardless of the presence of its maintenance debug file.
To continue monitoring and come back from the maintenance mode on the local
node, you must remove the "oc.debug" file on that node. It is the
user's responsibility to ensure that the Oracle Clusterware is properly
running after the maintenance phase.
For the ASMDG MNP (asm_dg.conf):
---------------------------
ORA_CRS_HOME
Oracle Clusterware home directory.
ORACLE_HOME
Oracle database home directory.
ORACLE_USER
HP-UX user name corresponding to the owner of Oracle software.
ASM_HOME
The home directory of Oracle where ASM is installed.
KILL_ASM_FOREGROUNDS
This parameter specifies if any ASM foreground processes that have file
descriptors open on the dismounted disk group volumes need to be killed or
not. This parameter can be set to either Yes or No(default Yes)
ASM_DISK GROUP
ASM Disk groups used by the database instance
ASM_VOLUME_GROUP:
Volume groups used in the ASM disk groups for this database instance.
CHECK_INTERVAL
Time interval in seconds (default 60) between consecutive checks of ASM
disk group status by the MNP.
MAINTENANCE_FLAG
ASMDG MNP maintenance mode: yes or no(default). This variable will enable
or disable maintenance mode for the ASMDG MNP. When the ASMDG MNP needs to
be maintained on one node, then this parameter must be set to yes and a
file "<ASMDG MNP working directory>/asm_dg.debug" must be created manually
on that node. During this maintenance period Oracle ASM disk group checking
is paused. Even if the Oracle ASM disk group is brought down on the local
node, the ASMDG MNP on that node will not be halted. To continue monitoring
and come back from the maintenance mode on one node, you must remove the
"asm_dg.debug" file on that node. It is the user's responsibility to ensure
that the Oracle ASM disk group is mounted properly after the maintenance
phase.
OC_TKIT_DIR
Set to OC MNP working directory. When the MAINTENANCE_FLAG is set to yes,
ASMDG MNP uses this parameter to check the OC MNP's maintenance status: If
the OC MNP MAINTENANCE_FLAG is set to yes and the oc.debug file is in the
OC_TKIT_DIR directory, the ASMDG MNP knows the OC MNP on the same node is
in maintenance mode. In this case, because of the dependency on the OC MNP,
the ASMDG MNP will go into maintenance mode as well regardless of the
presence of its debug file.
If MAINTENANCE_FLAG is no, OC_TKIT_DIR is not required, and ASMDG MNP will
not check the OC MNP maintenance status.
For the RAC MNP (rac_dbi.conf):
---------------------------
ORACLE_HOME
Oracle database home directory.
ORA_CRS_HOME
Oracle Clusterware home directory.
ORACLE_USER
HP-UX user name corresponding to the owner of Oracle software.
ORACLE_DBNAME
The database name.
START_MODE
Mode of instance start: mount, nomount or open (default).
STOP_MODE
Mode of instance stop: normal, transactional, immediate or abort (default).
If the RAC MNP fails, this Toolkit will use the "abort" option to halt the
RAC instance for a quick package shutdown regardless of the STOP_MODE value.
CHECK_INTERVAL
Time interval in seconds (default 60) between consecutive checks of RAC
Support for the SGeRAC Toolkit 105