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

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.
Figure 16 Internal structure of SGeRAC for Oracle Clusterware
92 SGeRAC Toolkit for Oracle RAC 10g or later