-
Create a local group and local user for Oracle in the new node.
The user and group ids for oracle must be the same as those on the other cluster nodes.
# groupadd -g 1000 oinstall
# groupadd -g 1001 dba
# groupadd -g 1002 oper
# useradd -u 999 -g oinstall -G dba,oper -d /oracle oracle
-
Create a password for the Oracle user on each node:
# passwd oracle
-
Make sure that the user Oracle can
remsh
between the nodes without having to use or confirm a password. If not, in the Oracle user account directory (for example, /oracle), create a .rhosts file that includes plus characters ("+ +") in the first line.
-
Create mount point directories for the Oracle base and CRS file system having the OCR and Vote Disk files.
-
Create the Oracle base mount point.
# mkdir /oracle
-
Create the mount point for the CRS file system having the OCR and Vote Disk files.
# mkdir /ora_crs
-
Create the mount point for the Oracle Database.
# mkdir /rac_db
-
Create the local CRS volume and the file system.
See Preparing $CRS_HOME on each node.
-
Plumb the private NIC and the virtual public IP addresses.
See Configuring private IP addresses for CRS.
See Creating public virtual IP addresses for Oracle.
-
Modify the VCS configuration as illustrated in the following example. Execute the following commands from one of the existing nodes. For example, galaxy or nebula.
-
Enable write access to the VCS configuration:
# haconf -makerw
-
Add the new node to the cluster:
# hasys -add saturn
-
If the ClusterService service group is configured, add the new node to its system list and specify a failover priority.
For example, add a node saturn with failover priority "2":
# hagrp -modify ClusterService SystemList -add saturn 2
-
If the ClusterService service group is configured, add the new node to its AutoStartList:
# hagrp -modify ClusterService AutoStartList \
galaxy nebula saturn
-
Configure the service groups on the new node (saturn). For example, to add the CVM service group:
-
Add the node to the CVMCluster resource by adding it to the CVMNodeId attribute key list:
# hares -modify cvm_clus CVMNodeId -add saturn 2
-
Add the resource for the PrivNIC network interfaces.
# hares -modify ora_priv Device lan1 0 lan2 1 -sys saturn
-
Add the resource for the PrivNIC IP address.
# hares -modify ora_priv Address "10.10.19.23" -sys saturn
-
Add the new node information for other VCS resources that exist.
-
Save the new configuration to disk:
# haconf -dump -makero
-
On each of the existing nodes, enable the nodes to recognize the new node.
# /opt/VRTS/bin/vxclustadm -m vcs -t gab reinit
-
Restart the new node.
# /usr/sbin/shutdown -r now
As the new node boots, VCS propagates the configuration from the existing cluster nodes to the new node. All the configuration files located in the /etc/VRTSvcs/conf/config directory, including main.cf, CVMTypes.cf, CFSTypes.cf, and OracleTypes.cf are identical on each node.
-
At this point, GAB membership shows membership for all the nodes. Following ports must be up on all the nodes:
# gabconfig -a
GAB Port Memberships
==============================================================
Port a gen df205 membership 012
Port b gen df20e membership 012
Port d gen df20f membership 012
Port f gen df219 membership 012
Port h gen df211 membership 012
Port o gen df208 membership 012
Port v gen df215 membership 012
Port w gen df217 membership 012