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

placement error" occurs, indicating that CRS is not ready to start the instance, the function sleeps for

2 minutes and then retries. At most 3 attempts are made to start the instance.

The stop function executes su to the Oracle software owner user id. It then determines the Oracle

instance id on the current node for the specified database using srvctl status database. Then it stops

the corresponding Oracle RAC instance using srvctl stop instance. If the user configurable parameter

STOP_MODE is abort and Oracle RAC Instance is not halted by srvctl command within

ORA_SHUTDOWN_TIMEOUT seconds, the Oracle RAC instance is terminated via killing its

background processes.

The check function executes ps and crs_stat commands to determine the health of RAC instance.

When the Oracle database instance MNP is in maintenance mode, the RAC instance health checking

is paused. Otherwise, in a continuous loop driven by a configurable timer, the check function runs ps

to check the number of the monitored RAC instance background processes. If one or more RAC

background processes are gone and crs_stat command shows Oracle Clusterware has not restarted

the Oracle RAC instance, the function will report the RAC instance as down. It means that the RAC

instance has either failed or been inappropriately shut down, that is, without using cmhaltpkg. The

service that invokes the function fails at this point and the SGeRAC package manager fails the

corresponding RAC database MNP instance.

How Serviceguard Extension for RAC Toolkit interacts with storage

management subsystems

The core concept of the Toolkit, namely, configuring an MNP for Oracle Clusterware and for each

RAC database, and configuring a dependency of each RAC database MNP on the Oracle

Clusterware MNP, holds true across all the storage management options supported by SGeRAC:

SLVM, CVM, ASM over SLVM, ASM over raw device (on HP-UX 11i v3) and CFS. However, the

storage management option deployed will have some impact on the configuration of the toolkit.

Use Case 1: Oracle Clusterware storage and database storage in SLVM/CVM

Figure 2. Use Case 1 setup

In this case, Oracle Clusterware quorum and registry device data and RAC database files are stored

in raw logical volumes managed by SLVM or CVM. The management of SLVM or CVM storage for

Oracle Clusterware and database is specified in the package configuration of the respective MNPs.

Use Case 2: Oracle Clusterware storage and database storage in CFS

In this case, Oracle Clusterware quorum and registry device data is stored in files in a CFS. Oracle

database files are also stored in a CFS.

For each CFS used by Oracle Clusterware for its quorum and registry device data, there will be a

dependency configured from the Oracle Clusterware MNP to the mount point MNP corresponding to

that CFS. The mount point MNP has a dependency on the CFS system MNP (SMNP).

Oracle

Clusterware MNP

RAC DB instance

MNP