Using Serviceguard Extension for RAC, 7th Edition, September 2008

ManualsBrandsHP ManualsSoftwareHP Serviceguard Extension for RAC (SGeRAC)

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.

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

# Quorum Server Parameters. Use the QS_HOST, QS_POLLING_INTERVAL,

# and QS_TIMEOUT_EXTENSION parameters to define a quorum server.

# The QS_HOST is the host name or IP address of the system

# that is running the quorum server process. The

# QS_POLLING_INTERVAL (microseconds) is the interval at which

# Serviceguard checks to make sure the quorum server is running.

# The optional QS_TIMEOUT_EXTENSION (microseconds) is used to increase

# the time interval after which the quorum server is marked DOWN.

# The default quorum server timeout is calculated from the

# Serviceguard cluster parameters, including NODE_TIMEOUT and

# HEARTBEAT_INTERVAL. If you are experiencing quorum server

# timeouts, you can adjust these parameters, or you can include

# the QS_TIMEOUT_EXTENSION parameter.

# The value of QS_TIMEOUT_EXTENSION will directly effect the amount

# of time it takes for cluster reformation in the event of failure.

# For example, if QS_TIMEOUT_EXTENSION is set to 10 seconds, the cluster

# reformation will take 10 seconds longer than if the QS_TIMEOUT_EXTENSION

# was set to 0. This delay applies even if there is no delay in

# contacting the Quorum Server. The recommended value for

# QS_TIMEOUT_EXTENSION is 0, which is used as the default

# and the maximum supported value is 30000000 (5 minutes).

50 Serviceguard Configuration for Oracle 10g RAC