Sample Configuration with HP Serviceguard Extension for RAG and Oracle Real Application Clusters 11g release 2 using Cluster File System

Running package racp on node ccia1

Successfully started package racp on node ccia1

Running package racp on node ccia2

Successfully started package racp on node ccia2

cmrunpkg: All specified packages are running

# cmviewcl

CLUSTER STATUS

cluster_ccia up

NODE STATUS STATE

ccia1 up running

ccia2 up running

MULTI_NODE_PACKAGES

PACKAGE STATUS STATE AUTO_RUN SYSTEM

SG-CFS-pkg up running enabled yes

SG-CFS-DG-1 up running enabled no

SG-CFS-MP-1 up running enabled no

SG-CFS-MP-2 up running enabled no

SG-CFS-MP-3 up running enabled no

crsp up running enabled no

racp up running enabled no

Verify OC status

# /u01/app/11.2.0/crs/bin/crsctl check crs

CRS-4638: Oracle High Availability Services is online

CRS-4537: Cluster Ready Services is online

CRS-4529: Cluster Synchronization Services is online

CRS-4533: Event Manager is online

Verify Oracle RAC database status

# /u01/app/11.2.0/crs/bin/srvctl status database -d orcl

Instance orcl1 is running on node ccia1

Instance orcl2 is running on node ccia2

Start and stop cluster

The following sections describe the process for starting and stopping OC 11g R2.

Start and stop OC 11g R2

Starting and stopping OC in SG packages helps ensure that the shared storage required by OC is

available.

When halting the SG cluster (

cmhaltcl –f), the package dependency ensures that the OC package

is halted before the cluster file systems are unmounted.

When

crsctl stop crs is used to stop OC while Oracle RAC instances are running, stopping OC

causes the instances to shut down in abort mode. This is the default behavior because other shutdown

modes may not complete in time for OC to stop in a timely manner.

If a different Oracle RAC instance shutdown mode (for example, normal or immediate) is desired, the

instances should be halted prior to initiating OC shutdown.