Extending the Oracle Grid Infrastructure Home to the New Node
Now that the new node has been configured to support Oracle Clusterware, you use Oracle Universal Installer (OUI) to
add a Grid home to the node being added to your cluster.
This section assumes that you are adding a node named racnode3 and that you have successfully installed Oracle Clusterware on racnode1 in a nonshared home,
where Grid_home represents the successfully installed Oracle Clusterware home.
To extend the Oracle Grid Infrastructure for a cluster home to include the new node:
Verify the new node has been properly prepared for an Oracle Clusterware installation by running the following CLUVFY command on the racnode1 node:
cluvfy stage -pre nodeadd -n racnode3 -verbose
As the oracle user (owner of the Oracle Grid Infrastructure for a cluster software installation) on racnode1,
go to Grid_home/oui/bin and run the addNode.sh script in silent mode:
If you are using Grid Naming Service (GNS):
./addNode.sh -silent "CLUSTER_NEW_NODES={racnode3}"
If you are not using Grid Naming Service (GNS):
./addNode.sh -silent "CLUSTER_NEW_NODES={racnode3}" "CLUSTER_NEW_VIRTUAL_
HOSTNAMES={racnode3-vip}"
When running this command, the curly braces ( { } ) are not optional and must be included or the command returns an error.
You can alternatively use a response file instead of placing all the arguments in the command line.
See Oracle Clusterware Administration and Deployment Guide for more information on using response files.
When the script finishes, run the root.sh script as the root user on the new node, racnode3, from the Oracle home directory on that node.
If you are not using Oracle Grid Naming Service (GNS), then you must add the name and address for racnode3 to DNS.
You should now have Oracle Clusterware running on the new node. To verify the installation of Oracle Clusterware on the new node,
you can run the following command on the newly configured node, racnode3:
$ cd /u01/app/11.2.0/grid/bin
$ ./cluvfy stage -post nodeadd -n racnode3 -verbose
Note:
Avoid changing host names after you complete the Oracle Clusterware installation, including adding or deleting domain qualifications.
Nodes with changed host names must be deleted from the cluster and added back with the new name.
See Also:
"Completing the Oracle Clusterware Configuration"
Oracle Real Application Clusters Administration and Deployment Guide for more information about adding and removing nodes from your cluster database
Extending the Oracle RAC Home Directory
Now that you have extended the Grid home to the new node, you must extend the Oracle home on racnode1 to racnode3.
The following steps assume that you have completed the tasks described in the previous sections,
"Preparing the New Node" and "Extending the Oracle Grid Infrastructure Home to the New Node",
and that racnode3 is a member node of the cluster to which racnode1 belongs.
The procedure for adding an Oracle home to the new node is very similar to the procedure you just completed for extending the Grid home to the new node.
To extend the Oracle RAC installation to include the new node:
Ensure that you have successfully installed the Oracle RAC software on at least one node in your cluster environment. To use these procedures as shown,
replace Oracle_home with the location of your installed Oracle home directory.
Go to the Oracle_home/oui/bin directory on racnode1 and run the addNode.sh script in silent mode as shown in the following example:
$ cd /u01/app/oracle/product/11.2.0/dbhome_1/oui/bin
$ ./addNode.sh -silent "CLUSTER_NEW_NODES={racnode3}"
When the script finishes, run the root.sh script as the root user on the new node, racnode3, from the Oracle home directory on that node.
For policy-managed databases with Oracle Managed Files (OMF) enabled, no further actions are needed.
For a policy-managed database, when you add a new node to the cluster, it is placed in the Free pool by default.
If you increase the cardinality of the database server pool, then an Oracle RAC instance is added to the new node, racnode3,
and it is moved to the database server pool. No further action is necessary.
Add shared storage for the undo tablespace and redo log files.
If OMF is not enabled for your database, then you must manually add an undo tablespace and redo logs.
If you have an administrator-managed database, then add a new instance on the new node as described in "Creating an Instance on the New Node".
If you followed the installation instructions in this guide, then your cluster database is an administrator-managed database
and stores the database files on Oracle Automatic Storage Management (Oracle ASM) with OMF enabled.
After completing these steps, you should have an installed Oracle home on the new node.
See Also:
"Verifying Your Oracle RAC Database Installation"
Oracle Real Application Clusters Administration and Deployment Guide for more information about adding and removing nodes from your cluster database
Adding the New Node to the Cluster using Enterprise Manager