In this Document
Purpose
Scope and Application
Installing Oracle Clusterware Using a Cluster Configuration File
Scalability RAC Community
References
Applies to:
Oracle Universal Installer - Version: 10.2.0.1 to 11.2.0.3 - Release: 10.2 to 11.2
Information in this document applies to any platform.
Purpose
The purpose of this document is to provide information on using the CLUSTER CONFIGURATION FILE.
Scope and Application
This document is intended for RAC DBA's and support analysts installing 10g/11gR1 CRS or 11gR2 Grid Infrastructure.
Installing Oracle Clusterware Using a Cluster Configuration File
During installation of Oracle Clusterware, on the Specify Cluster
Configuration page, you are given the option either of providing cluster
configuration information manually, or of using a cluster configuration
file. A cluster configuration file is a text file that you can create
before starting OUI, which provides OUI with information about the
cluster name and node names that it needs to configure the cluster.
Oracle suggests that you consider using a cluster configuration file if
you intend to perform repeated installations on a test cluster, or if
you intend to perform an installation on many nodes.
To create a cluster configuration file for 10g and 11gR1:
1. On the installation media, navigate to the directory Disk1/response directory.
2. Using a text editor, open the response file crs.rsp, and find the section CLUSTER_CONFIGURATION_FILE.
3. Follow the directions in that section for creating a cluster configuration file.
Example output from the crs.rsp file CLUSTER_CONFIGURATION_FILE section:
###############################################################################
# The following entries can be used to specify cluster information for silent #
# installs. Note that you can specify values for sl_tableList OR #
# CLUSTER_CONFIGURATION_FILE, but you need not specify both. #
# #
# Also note that if you are cloning an existing installation, you shoud use #
# sl_tableList. Specifying CLUSTER_CONFIGURATION_FILE for a clone install #
# will not work. #
###############################################################################
#------------------------------------------------------------------------------
#Name : s_clustername
#Datatype : String
#Description: The name of the Cluster you are creating.
#
# The maximum length allowed for clutername is 15 characters. Valid
# characters can be any combination of lower and uppercase alphabets
# (A - Z), (0 - 9), hyphen(-) and underscore(_).
#------------------------------------------------------------------------------
s_clustername=<Value Unspecified>
#------------------------------------------------------------------------------
#Name : sl_tableList
#Datatype : StringList
#Description: Contains a list of public node names, private node names, and
# virtual hostnames to be part of the cluster.
#
# The list is a comma-separated list of nodes. Each entry in the
# list should be a colon-separated string that contains 5 fields.
# The fields should be ordered as follows:
# 1. The first field is for public node name.
# 2. The 2nd field is for private node name,
# 3. The 3rd field is for virtual host name
# 4. The 4th & 5th fields should not be modified, and should remain
# as "N:Y"
#
#Example : {"n1:n1-priv:n1-vip:N:Y","n2:n2-priv:n2-vip:N:Y"}
#------------------------------------------------------------------------------
sl_tableList=<Value Unspecified>
#------------------------------------------------------------------------------
#Name : CLUSTER_CONFIGURATION_FILE
#Datatype : String
#Description: Use to specify the location of the Cluster Configuration File.
#
# The Cluster Configuration File (CCF) is an alternative file that
# can be used in place of sl_tableList. If you are using
# sl_tableList, you do not need to specify a location for this
# file. Instead you should leave the value as "".
#
# The CCF is primarily used for interactive installations to
# quickly populate the Cluster Configuration Dialog with node
# information, and is useful when specifying large numbers of
# nodes, but it can also be used for silent installations. The
# CCF is a simply formatted file that contains whitespace
# delimited information about your cluster. As an
# example, specifying a two node cluster with a Cluster Name of
# "MyCluster" could be done with using a file with the following
# contents:
# -------------------------
# MyCluster
#
# node1 node1-priv node1-vip
# node2 node2-priv node2-vip
# -------------------------
#
# NOTE: You cannot use this variable if you are cloning an existing
# Oracle Clusterware installation. If you are cloning an
# existing installation, you must use sl_tableList to
# specify new cluster information. This variable can be
# used for normal silent installations that are not a clone
# of an existing installation.
#
#Example : CLUSTER_CONFIGURATION_FILE = "/tmp/mycluster.conf"
#------------------------------------------------------------------------------
CLUSTER_CONFIGURATION_FILE=""
To create a cluster configuration file for 11gR2:
To create a cluster configuration file manually, start a text editor, and create a file that provides the name of the public and virtual IP addresses for each cluster member node, in the following format and save the file name with .ccf:
node1 node1-vip
node2 node2-vip
.
.
.
For example /tmp/grid.ccf:
mynode1 mynode1-vip
mynode2 mynode2-vip
Scalability RAC Community
To
discuss this topic further with Oracle experts and industry peers, we
encourage you to review, join or start a discussion in the My Oracle Support Scalability RAC Community.
References
"Oracleî Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide 10g Release 2 (10.2) for Linux"
"Oracle Clusterware and Oracle Real Application Clusters Installation and Configuration Guide for Microsoft Windows Platforms"
浙公网安备 33010602011771号