Installing Oracle Grid Infrastructure Using a Cluster Configuration File

During installation of Oracle Grid Infrastructure, you have the option of either providing cluster configuration information manually, or using a cluster configuration file.

A cluster configuration file is a text file that you can create before starting gridSetup.sh, which provides the installer with cluster node addresses that it requires to configure the cluster.

Oracle recommends 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. A sample cluster configuration file is available in the directory Grid_home/install/response/sample.ccf.

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:

node1 node1-vip /node-role 
node2 node2-vip /node-role 
.
.
.

node-role can have either HUB or LEAF as values. Specify the different nodes, separating them with either spaces or colon (:).

For example:

mynode1 mynode1-vip /HUB
mynode2 mynode2-vip /LEAF

Or, for example:

mynode1:mynode1-vip:/HUB
mynode2:mynode2-vip:/LEAF

Example 9-1 Sample Cluster Configuration File

The following sample cluster configuration file is available in the directory Grid_home/install/response/sample.ccf:

# 
# Cluster nodes configuration specification file
# 
# Format:
# node [vip] [role-identifier] [site-name]
# 
# node            - Node's public host name
# vip             - Node's virtual host name
# role-identifier - Node's role with "/" prefix - should be "/HUB" or "/LEAF"
# site-name       - Node's assigned site
# 
# Specify details of one node per line.
# Lines starting with '#' will be skipped.
# 
# (1) vip and role are not required for Oracle Grid Infrastructure software only
#     installs and Oracle Member cluster for Applications
# (2) vip should be specified as AUTO if Node Virtual host names are Dynamically
#     assigned
# (3) role-identifier can be specified as "/LEAF" only for "Oracle Standalone Cluster"
# (4) site-name should be specified only when configuring Oracle Grid Infrastructure with "Extended Cluster" option
# 
# Examples:
# --------
# For installing GI software only on a cluster:
# ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
# node1
# node2
#
# For Standalone Cluster:
# ^^^^^^^^^^^^^^^^^^^^^^
# node1 node1-vip /HUB
# node2 node2-vip /LEAF
#
# For Standalone Extended Cluster:
# ^^^^^^^^^^^^^^^^^^^^^^
# node1 node1-vip /HUB sitea
# node2 node2-vip /LEAF siteb
#
# For Domain Services Cluster:
# ^^^^^^^^^^^^^^^^^^^^^^^^^^^
# node1 node1-vip /HUB
# node2 node2-vip /HUB
#
# For Member Cluster for Oracle Database:
# ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
# node1 node1-vip /HUB
# node2 node2-vip /HUB
#
# For Member Cluster for Applications:
# ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
# node1
# node2
#

Parent topic: Installing Oracle Grid Infrastructure