Sample Configurations with SGeRAC and Oracle RAC 10gR2, March 2009

12. Choose Recovery Configuration

a. In this sample, use default parameters (no flash recovery and archiving.).

b. Flash Recovery Area and archiving can be configured. When configuring archiving,

choose Enable Archive Mode Parameter and specify where to place archive logs. If

Flash Recovery Area is configured, archive logs default to the Flash Recovery area.

c. Without CFS, for simplicity, the archives logs should be on a file system that can be

accessed by any node that would be performing a database recovery.

13. Select Database Content

14. Configure Database Services

15. Configure Initialization Parameters

16. Configure Database Storage

17. Create Database

Configuring Serviceguard packages using Serviceguard Extension for RAC

It is recommended to start and stop Oracle Cluster Software in a Serviceguard package, as that will

ensure that Oracle Cluster Software will start after SGeRAC is started and will stop before SGeRAC is

halted. Serviceguard packages should also be used to synchronize storage activation and

deactivation with Oracle Cluster Software and RAC instances. Additionally, the Serviceguard

package also checks CSS in case CSS is halted outside the package. If CSS is halted outside the

package, the package halts.

For SGeRAC A.11.17, there is a whitepaper Use of Serviceguard Extension For RAC Toolkit with

Oracle RAC 10g Release 2 or later (http://docs.hp.com/en/8987/sgeractoolkit-wp.pdf) to configure

packages with multi-node packages and simple dependency features. The SGeRAC Toolkit can be

downloaded from the software depot (http://software.hp.com/ à High availability à Serviceguard

Extension for RAC Toolkit).

SGeRAC A.11.18 and later includes the SGeRAC Toolkit along with a README document describing

the use of SGeRAC Toolkit.

Prepare Oracle Cluster Software for Serviceguard packages

# export ORA_CRS_HOME=/mnt/app/crs/oracle/product/10.2.0/crs

# export PATH=$PATH:$ORA_CRS_HOME/bin

Stop Oracle Clusterware on each node

For 10g 10.2.0.1 or later:

# crsctl stop crs

Wait until Oracle Cluster Software completely stops. (Check CRS logs or check for Oracle processes,

for example ps –ef | grep ocssd.bin)

Change Oracle Cluster Software from starting at boot time on each node

For 10g 10.2.0.1 or later:

# crsctl disable crs

Creating Serviceguard packages

In this configuration, the cluster is configured with one Serviceguard package multi-node package that

will start and stop Oracle Clusterware.