Using Serviceguard Extension for RAC, 9th Edition, September 2010

ManualsBrandsHP ManualsSoftwareHP Serviceguard Extension for RAC (SGeRAC)

and to build the correct Oracle runtime executables. When the executables are installed to a

cluster file system, the Oracle installer has an option to install the executables once. 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 either the

character (raw) device files names for the logical volumes created earlier, or the database can

reside on a cluster file system.

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

Oracle File Names for Demo Database ”, earlier in this chapter. As the installer prompts for the

database file names, use the pathnames of the raw logical volumes instead of using the defaults.

NOTE: 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 A.11.19 version of the 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 SGeRAC_Cluster

# 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 lock LUN

# the quorom 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.

# Lock Disk Parameters. Use the FIRST_CLUSTER_LOCK_VG and

# FIRST_CLUSTER_LOCK_PV parameters to define a lock disk.

# The FIRST_CLUSTER_LOCK_VG is the LVM volume group that

# holds the cluster lock. This volume group should not be

# used by any other cluster as a cluster lock device.

# LUN lock disk parameters. Use the CLUSTER_LOCK_LUN parameter

# to define the device on a per node basis. The device may only

# be used for this purpose and by only a single cluster.

# Example for a FC storage array cluster disk

# CLUSTER_LOCK_LUN /dev/dsk/c1t2d3s1

# For 11.31 and later versions of HP-UX

# CLUSTER_LOCK_LUN /dev/disk/disk4_p2

# Quorum Server Parameters. Use the QS_HOST, QS_ADDR, QS_POLLING_INTERVAL,

# and QS_TIMEOUT_EXTENSION parameters to define a quorum server. The QS_HOST

# and QS_ADDR are either the host name or IP address of the system that is

# running the quorum server process. More than one IP address can be

Cluster Configuration ASCII File 83