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

(on HP-UX 11i v3) or shared raw logical volumes managed by SGeRAC using

SLVM.

The responsibilities of Oracle Clusterware in this combined environment include:

• Management of the database and associated resources (database instances, services, virtual IP

addresses (VIPs), listeners, etc.)

• Management of Oracle ASM instances, if configured

All pieces of the combined stack must start up and shut down in the proper sequence and we need to

be able to automate the startup and shutdown sequences, if desired. In particular, the storage needed

for the operation of Oracle Clusterware must be started up before the Oracle Clusterware processes

are started, and the storage needed for the operation of a RAC database instance has to be started

before the instance is started. On shutdown, the sequence is reversed, that is, Oracle Clusterware and

the RAC database instance must be halted before deactivating the storage needed by these two

entities.

Traditionally, in the SG and SGeRAC environment, these ordering requirements have been met using

a package to encapsulate the startup and shutdown of an application as well as the startup and

shutdown of storage needed by that application. In SG and SGeRAC, a different model is introduced

for the case where the storage needs of an application are met by using a CFS. Here the CFS is

started up and shutdown in a separate package from the one that starts up and shuts down the

application. The ordering requirement is met by using the SGeRAC feature of simple package

dependencies, discussed later in this document.

Can we manage the storage needs of Oracle Clusterware and RAC database instances in Oracle

RAC, using SGeRAC packages in the ways just discussed? Starting in Oracle 10.1.0.4, Oracle made

the following improvements in coordination between Oracle Clusterware and platform clusterware,

enabling such use of SGeRAC packages:

Support for on-demand startup and shutdown of Oracle Clusterware and RAC database instances.

• In addition to starting up and shutting down Oracle Clusterware automatically as HP-UX 11i is

taken up to init level 3 and taken down to a lower level respectively, we can start up and shut down

Oracle Clusterware on demand.

• To disable the automatic startup of Oracle Clusterware on entering init level 3, we use the “crsctl

disable crs” command. Oracle Clusterware may thereafter be started up and shut down on

demand using the commands “crsctl start crs” and “crsctl stop crs” respectively.

• In addition to starting up and shutting down the RAC database instance automatically as Oracle

Clusterware itself is started up and shut down, we can start up and shut down the RAC database

instance on demand.

• To disable the automatic startup of the RAC database instance with the startup of Oracle

Clusterware, we follow the procedures described by Oracle to remove auto-start for the instance.

The RAC database instance may thereafter be started up and shut down on demand by, for

example, using the command “srvctl start instance...” and “srvctl stop

instance...” respectively.

Support for invocation of Oracle Clusterware commands from customer-developed scripts

Contact HP representative for the detail.

See Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide 10g Release 2 (10.2) at

http://www.oracle.com/pls/db102/portal.portal_db?selected=4

See Doc ID: Note:298073.1 HOW TO REMOVE CRS AUTO START AND RESTART FOR A RAC INSTANCE at https://metalink.oracle.com/

(Oracle MetaLink account required)