HP Serviceguard Extension for RAC (SGeRAC) manual SGeRAC Toolkit for Oracle RAC 10g or later

3.The user can maintain the Oracle ASM disk groups on that node while Oracle ASMDG MNP package is still running.

4.After the maintenance work is completed, the user can remove the created asm_dg.debug in step 2 to bring the Oracle ASMDG MNP package out of maintenance mode to resume normal monitoring by Serviceguard. The maintenance mode message will appear in the Oracle database instance package log files, e.g. “Starting ASM DG MNP checking again after maintenance.”

Use Case 3: performing maintenance with Oracle RAC database instance

1.Make sure the MAINTENANCE_FLAG parameter for Oracle database instance MNP is set to yes when this packages is created. If not, shutdown this first, set the MAINTENANCE_FLAG to yes, and then restart MNP.

2.On the maintenance node, create a debug file called rac.debug file in the Oracle database instance MNP working directory. The Oracle database instance MNP on this node will go into maintenance mode. The maintenance mode message will appear in Oracle database instance package log files, e.g. “RAC MNP pausing RAC instance checking and entering maintenance mode.”

3.The user can maintain the Oracle database instance on that node while Oracle database instance package is still running.

4.After the maintenance work is completed, the user can remove the created rac.debug in step 2 to bring the Oracle database instance package out of maintenance mode to resume normal monitoring by Serviceguard. The maintenance mode message will appear in the Oracle database instance package log files, e.g. “Starting RAC MNP checking again after maintenance.”

Serviceguard Extension for RAC Toolkit internal file structure

There is a set of files in SGeRAC that deal with SGeRAC specific configuration and logic, and a different set of files that deal with Oracle Clusterware, ASMDG MNP, and RAC specific logic, with a bridge in between.

On the SGeRAC-specific side is the MNP ASCII configuration file and the control script (for legacy packages), or module script (for modular packages). The ASCII configuration file parameters are stored in the SGeRAC configuration database, at cmapplyconf time, and are used by the package manager in its actions on behalf of this package. The control script or module script invokes the Oracle Clusterware specific functions for start, stop, and check through the bridge script.

On the Oracle Clusterware specific side, there is a configuration file (oc.conf) that is sourced by the start, stop and check script files (oc.sh and oc.check). The bridge script (toolkit_oc.sh) allows the start, stop, and check calls to remain unaffected by changes in the Oracle Clusterware specific scripts. A similar set of files deals with RAC instance specific logic.

Figure 19 shows the internal file structure of the toolkit for Oracle Clusterware. Figure 20 shows the similar internal file structure of the toolkit for the ASMDG MNP. Figure 21 shows the similar internal file structure of the toolkit for the RAC DB instance.

90 SGeRAC Toolkit for Oracle RAC 10g or later