HP Serviceguard Extension for RAC (SGeRAC) manual Asmdisk Group

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 instance status by the MNP.

ORA_RESTART_TIMEOUT

Time interval in seconds (default 180) for the Toolkit script to wait for Oracle to restart an instance which is terminated prematurely before exiting the package.

ORA_SHUTDOWN_TIMEOUT

Time interval in seconds (default 120) for the Toolkit script to wait for the Oracle abort to complete before killing the Oracle background processes. The ORA_SHUTDOWN_TIMEOUT variable is used to protect against a worst-case scenario where a hung database prevents the package halt script from completing. The value of ORA_SHUTDOWN_TIMEOUT must be less than the HALT_SCRIPT_TIMEOUT value set in the rac package configuration file.

MAINTENANCE_FLAG

RAC MNP maintenance mode: yes or no (default). This variable will enable or disable maintenance mode for the RAC MNP.

When the RAC MNP needs to be maintained on one node, this parameter must be set to yes and a file "<RAC MNP working directory>/rac.debug" needs to be created manually on that node. During this maintenance period the Oracle RAC instance's process checking is paused. Even if the Oracle RAC instance is brought down on the local node, the RAC MNP on that node will not be halted.

To continue monitoring and come back from the maintenance mode on one node, you should remove the "rac.debug" file on that node. It is the user's responsibility to ensure that the Oracle RAC instance is properly running after the maintenance phase.

104 SGeRAC Toolkit for Oracle RAC 10g or later