Using Serviceguard Extension for RAC, 6th Edition, April 2008

Installing Oracle Real Application Clusters

NOTE: Some versions of Oracle RAC requires installation of additional software.

Refer to your version of Oracle for specific requirements.

Before installing the Oracle Real Application Cluster software, make sure the storage

cluster is running. Login as the oracle user on one node and then use the Oracle installer

to install Oracle software and to build the correct Oracle runtime executables. When

executables are installed to a local file system on each node, the Oracle installer copies

the executables to the other nodes in the cluster.

For details on Oracle installation, refer to the Oracle installation documentation. As

part of this installation, the Oracle installer installs the executables and optionally, the

Oracle installer can build an Oracle demo database on the primary node. The demo

database files can be the character (raw) device files names for the logical volumes

create earlier.

For a demo database on SLVM or CVM, create logical volumes as shown in Table 2-1:

“Required Oracle File Names for Demo Database ”. As the installer prompts for the

database file names, either the pathnames of the raw logical volumes instead of using

the defaults. If you do not wish to install the demo database, select install software

only.

Cluster Configuration ASCII File

The following is an example of an ASCII configuration file generated with the

cmquerycl command using the -w full option on a system with Serviceguard

Extension for RAC. The OPS_VOLUME_GROUP parameters appear at the end of the file.

# **********************************************************************

# ********* HIGH AVAILABILITY CLUSTER CONFIGURATION FILE ***************

# ***** For complete details about cluster parameters and how to *******

# ***** set them, consult the Serviceguard manual. *********************

# **********************************************************************

# Enter a name for this cluster. This name will be used to identify the

# cluster when viewing or manipulating it.

CLUSTER_NAME cluster 1

# Cluster Lock Parameters

# The cluster lock is used as a tie-breaker for situations

# in which a running cluster fails, and then two equal-sized

# sub-clusters are both trying to form a new cluster. The

# cluster lock may be configured using only one of the

# following alternatives on a cluster:

# the LVM lock disk

# the quorum server

# Consider the following when configuring a cluster.

# For a two-node cluster, you must use a cluster lock. For

# a cluster of three or four nodes, a cluster lock is strongly

# recommended. For a cluster of more than four nodes, a

# cluster lock is recommended. If you decide to configure

# a lock for a cluster of more than four nodes, it must be

# a quorum server.

64 Serviceguard Configuration for Oracle 10g RAC