Using Serviceguard Extension for RAC Version A.11.20 - (August 2011)

dependent on Oracle Clusterware MNP. Disk groups that are exclusively used by a RAC DB should
be managed in separate ASM DG MNP. If different RAC Database uses different ASM Disk groups
then those, ASM DGs should not be configured in a single ASMDG MNP. As RAC DB Instance
MNP 3 and RAC DB Instance MNP 4 use completely different ASM diskgroups, they are made
dependent on their respective ASMDG MNP(ASMDG MNP 2, ASMDG MNP 3). However, If two
RAC DB use same set of ASM Disk groups, then those ASM DG can be configured in a single
ASMDG MNP. Then, both the RAC MNP is made dependent on the ASMDG MNP. RAC DB
Instance MNP 1, RAC DB Instance MNP 2 makes use of same set of ASM diskgroups so both
MNPs are made dependent on ASMDG MNP 1.
How to create a Serviceguard Extension for RAC modular package
In SGeRAC A.11.19, SGeRAC introduces modular package format. With this feature, the user
can use the single SGeRAC package interface to manage SGeRAC Toolkit to simplify Toolkit
management. For more information see, “Support for the SGeRAC Toolkit” (page 92) section.
How Serviceguard Extension for RAC Toolkit maintenance mode works
As of SGeRAC A.11.18, SGeRAC Toolkit supports the maintenance mode, so the user can maintain
Oracle Clusterware and Oracle database instance without halting Oracle Clusterware MNP and
Oracle database instance MNP. Beginning with the SGeRAC A.11.19 patches, PHSS_40885
(11i v2) and PHSS_40886 (11i v3), SGeRAC toolkit also supports the maintenance mode of
ASMDG MNP—the user can maintain ASM DG included in ASMDG MNP without halting the
MNP. The MAINTENANCE_FLAG parameter is specified in the respective toolkit configuration files.
Use Case 1: Performing maintenance with Oracle Clusterware
Oracle Clusterware MNP, ASMDG MNP (if configured) and the Oracle database instance MNP
go into maintenance mode.
1. Make sure the MAINTENANCE_FLAG parameter for Oracle Clusterware MNP, is set to yes
when these packages are created. If not, shutdown the MNPs first, set the MAINTENANCE_FLAG
to yes, and then restart MNPs.
2. On the maintenance node, create a debug file called oc.debug in the Oracle Clusterware
MNP working directory. All the three MNPs 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, ASM disk groups, 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 OC MNP package
log files, e.g. “Starting Oracle Clusterware checking again after maintenance.”
Use Case 2: performing maintenance with ASM disk groups
Only the Oracle ASMDG MNP goes into maintenance mode.
1. Make sure the MAINTENANCE_FLAG parameter for ASMDG MNP is set to yes when this
package is created. If not, shutdown this MNP first, set the MAINTENANCE_FLAG to yes, and
then restart the MNP.
2. On the maintenance node, create a debug file called asm_dg.debug file in the Oracle
ASMDG MNP working directory. The Oracle ASMDG MNP on this node will go into
maintenance mode. The maintenance mode message will appear in ASMDG MNP package
log files, e.g. “ASM DG MNP pausing ASM DG instance checking and entering maintenance
mode.”
Serviceguard Extension for RAC Toolkit operation 89