Using Serviceguard Extension for RAC Version A.11.20 - (August 2011)
membership information to the Oracle Clusterware and provides clustered
storage to meet the needs of Oracle Clusterware and RAC database instances.
The Oracle Clusterware manages the database and associated resources (e.g.
database instances, services, virtual IP addresses, listeners, etc), and ASM
instances if configured.
The startup and shutdown of the various components in the combined SGeRAC-Oracle
Clusterware configuration must be coordinated in the proper sequence. The storage
needed for the operation of Oracle Clusterware must be activated before the
Oracle Clusterware processes are started, and the storage needed for the operation
of a RAC database instance must be activated before the RAC database instance
is started. On shutdown, the sequence is reversed. Oracle Clusterware and the RAC
database instance must be halted before deactivating the storage needed by these
two entities.
The SGeRAC Toolkit provides the mechanism to coordinate the ordering of the
pieces in the combined SGeRAC/Oracle RAC stack and the dependency between the
Oracle Clusterware and Oracle RAC instances. Also, the Toolkit offers a
uniform, easy-to-manage and intuitive method to coordinate the operation
across the full range of storage management options supported by SGeRAC.
The SGeRAC Toolkit leverages multi-node package (MNP) and package dependency
features supported in SG/SGeRAC A.11.17 or later. In the SGeRAC Toolkit,
scripts for configuring three MNPs - Oracle Clusterware MNP (OC MNP), RAC
database instance MNP (RAC MNP) and Oracle Automatic Storage Management (ASM)
Diskgroup MNP (ASMDG MNP) are provided. The "OC MNP" allows SGeRAC to
start/stop and monitor Oracle Clusterware processes. The "RAC MNP" allows
SGeRAC to start/stop and monitor processes of a RAC database instance. The
"ASMDG MNP" allows mounting/unmounting and monitoring of the ASM Disk groups.
Since Oracle Clusterware must be running before any RAC database instances
can be started, RAC MNP packages are required to define a 'same node up'
package dependency on the OC MNP. When using ASM for storage management,
the ASM DG MNP must have a package dependency on the OC MNP and the
corresponding RAC MNP packages must have a "same node up" dependency on
the ASM DG MNP.
In SGeRAC, the Oracle Clusterware storage (Oracle Cluster Registry
and voting disk) can be configured as:
- Raw logical volumes managed by Shared Logical Volume Manager (SLVM)
or Cluster Volume Manager (CVM)
- Files managed by Cluster File System (CFS)
- Oracle Automatic Storage management (ASM) Disk Groups (from Oracle 11g R2)
The members of the ASM Disk Groups can be either shared raw logical volumes
managed by SLVM (ASM over SLVM) or HP-UX raw disks ( ASM over HP-UX raw disks)
In SGeRAC, the RAC database files can be configured as
- Raw logical volumes managed by Shared Logical Volume Manager (SLVM)
or Cluster Volume Manager (CVM)
- Files managed by Cluster File System (CFS)
- Oracle Automatic Storage management (ASM) Disk Groups (from Oracle 11g R2)
The members of the ASM Disk Groups can be either shared raw logical volumes
managed by SLVM (ASM over SLVM) or HP-UX raw disks ( ASM over HP-UX raw disks)
Dependency structure while using different storage management options
1. Dependency structure in the case of SLVM
--------------- ---------------
| | | |
| | | |
| OC-MNP |<--------| RAC-MNP |
| | | |
| | | |
--------------- ---------------
The SLVM Volume group used for Oracle Clusterware storage are configured in the
OC-MNP package.
The SLVM Volume group used for RAC database storage are configured in the RAC-MNP
package.
2. Dependency structure in the case of CFS
--------------- ---------------
| | | |
| | | |
| OC-MNP |<--------| RAC-MNP |
| | | |
| | | |
--------------- ---------------
| |
| |
| |
| |
V V
--------------- ---------------
| | | |
| | | |
| CFS-MP1-MNP | | CFS-MP2-MNP |
| | | |
| Holds OCR & | | Holds data |
| VOTE files | | base files |
Support for the SGeRAC Toolkit 93