Use of Serviceguard Extension for RAC Toolkit with Oracle RAC 10g Release 2 or later, March 2009

11
1. Make sure the MAINTENANCE_FLAG parameter for both the Oracle Clusterware MNP and the
Oracle database instance MNPs are set to yes when these packages are created. If not, shutdown
both MNPs first, set the MAINTENANCE_FLAG to yes on all nodes, then restart both MNPs.
2. On the maintenance node, create a debug file called oc.debug in the Oracle Clusterware MNP
working directory. Both Oracle Clusterware MNP and the Oracle database instance MNP on this
node will go into maintenance mode. The maintenance mode message will appear in the Toolkit
package log files, e.g. “OC MNP pausing Oracle Clusterware checking and entering
maintenance mode”.
3. The user can maintain the Oracle Clusterware and Oracle Database instance on that node while
Toolkit package is still running.
4. After the maintenance work is completed, the user can remove the created oc.debug in step 2 to
bring the Toolkit package out of maintenance mode and resume normal monitoring by
Serviceguard. The Toolkit in maintenance mode message will appear in Toolkit package log files,
e.g. “"Starting Oracle Clusterware checking again after maintenance”.
Use Case 2: Performance maintenance with Oracle RAC database instance
Only the Oracle database instance MNP goes into maintenance mode.
1. Make sure the MAINTENANCE_FLAG parameter for both the Oracle Clusterware MNP and the
Oracle database instance MNPs are set to yes when these packages are created. If not, shutdown
both MNPs first, set the MAINTENANCE_FLAG to yes on all nodes, then restart both MNPs.
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“. The Oracle Clusterware MNP will remain in normal working 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 and RAC specific logic, with a bridge in
between.
On the SGeRAC-specific side we have 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) which 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 4 shows the internal file structure of the toolkit for Oracle Clusterware. Figure 5 shows the
similar internal file structure of the toolkit for the RAC DB instance.