4 Adding and Deleting Cluster Nodes

Adding a Cluster Node on Linux and UNIX Systems

This procedure describes how to add a node to your cluster. This procedure assumes that:

• There is an existing cluster with a node named node1

• You are adding a node named node2

• You have successfully installed Oracle Clusterware on node1 in a nonshared home, where Grid_home represents the successfully installed home

To add a node:

1. Ensure that you have successfully installed Oracle Clusterware on at least one node in your cluster environment. To perform the following procedure, Grid_home must identify your successfully installed Oracle Clusterware home.

   See Also:

   Oracle Grid Infrastructure Installation Guide for Oracle Clusterware installation instructions

2. Verify the integrity of the cluster and node2:

   $ cluvfy stage -pre nodeadd -n node2 [-fixup [-fixupdir fixup_dir]] [-verbose]
   

   You can specify the -fixup option and a directory into which CVU prints instructions to fix the cluster or node if the verification fails.

3. Navigate to the Grid_home/oui/bin directory on node1 and run the addNode.sh script using the following syntax, where node2 is the name of the node that you are adding and node2-vip is the VIP name for the node:

   If you are using Grid Naming Service (GNS):

   $ ./addNode.sh -silent "CLUSTER_NEW_NODES={node2}"
   

   If you are not using GNS:

   $ ./addNode.sh -silent "CLUSTER_NEW_NODES={node2}""CLUSTER_NEW_VIRTUAL_HOSTNAMES={node2-vip}" 
   

   Alternatively, you can specify the entries shown in Example 4-1 in a response file, where file_name is the name of the file, and run the addNode.sh script, as follows:

   $ addNode.sh -silent -responseFile file_name
   

   When prompted, run root.sh before the addNode.sh script completes.

   Example 4-1 Response File Entries for Adding Oracle Clusterware Home

   RESPONSEFILE_VERSION=2.2.1.0.0
   
   CLUSTER_NEW_NODES = {"newnode2"}
   CLUSTER_NEW_VIRTUAL_HOSTNAMES = {"newnode2-vip"}
   

   See Also:

   Oracle Universal Installer and OPatch User's Guide for details about how to configure command-line response files

   Notes:

   • If you are not using Oracle Grid Naming Service (GNS), then you must add the name and address of node2 to DNS.

   • Command-line values always override response file values.

4. Check that your cluster is integrated and that the cluster is not divided into separate parts by running the following CVU command. This command verifies that any number of specific nodes has been successfully added to the cluster at the network, shared storage, and clusterware levels:

   $ cluvfy stage -post nodeadd -n node2 [-verbose]
   

   See Also:

   "cluvfy stage [-pre | -post] nodeadd" for more information about this CVU command

you can optionally extend Oracle Database with Oracle Real Application Clusters (Oracle RAC) components to the new nodes, making them members of an existing Oracle RAC database.

Deleting a Cluster Node on Linux and UNIX Systems

This section describes the procedure for deleting a node from a cluster.

To delete a node from a cluster:

1. Ensure that Grid_home correctly specifies the full directory path for the Oracle Clusterware home on each node, where Grid_home is the location of the installed Oracle Clusterware software.

2. If Cluster Synchronization Services (CSS) is not running on the node you are deleting, then the crsctl unpin css command in this step fails. Before you run the crsctl unpin css command, run the following command as either root or the user that installed Oracle Clusterware:

   $ olsnodes -s -t
   

   This command shows whether the node is active and whether it is pinned. If the node is unpinned, then you do not need to run the crsctl unpin css command.

   From any node that you are not deleting, run the following command from the Grid_home/bin directory as root to expire the CSS lease on the node you are deleting:

   # crsctl unpin css -n node_to_be_deleted
   

   Note:

   • You cannot unpin a node that has an instance of Oracle RAC that is older than 11g release 2 (11.2) if you installed Oracle Clusterware 11g release 2 (11.2) on that node.

   • If the node you are deleting is not accessible, then you can skip steps 3, 5, and 6.

3. Disable the Oracle Clusterware applications and daemons running on the node. Run the rootcrs.pl script as root from the Grid_home/crs/install directory on the node to be deleted, as follows:

   Note:

   Before you run this command, you must stop the EMAGENT.

   # ./rootcrs.pl -delete -force
   

   If you are deleting multiple nodes, then run this script on each node that you are deleting.

   Notes:

   • If you do not use the -force option in the preceding command or the node you are deleting is not accessible for you to execute the preceding command, then the VIP resource remains running on the node. You must manually stop and remove the VIP resource using the following commands as root from any node that you are not deleting:

     # srvctl stop vip -i vip_name -f
     # srvctl remove vip -i vip_name -f
     

     Where vip_name is the VIP for the node to be deleted. If you specify multiple VIP names, then separate the names with commas and surround the list in double quotation marks ("").

   • If the node you are deleting is not accessible, then you can skip steps 5 and 6.

4. From any node that you are not deleting, run the following command from the Grid_home/bin directory as root to delete the node from the cluster:

   # crsctl delete node -n node_to_be_deleted
   

5. On the node you want to delete, run the following command as the user that installed Oracle Clusterware from the Grid_home/oui/bin directory where node_to_be_deleted is the name of the node that you are deleting:

   $ ./runInstaller -updateNodeList ORACLE_HOME=Grid_home "CLUSTER_NODES=
   {node_to_be_deleted}" CRS=TRUE -local
   

6. On the node that you are deleting, run the runInstaller command as the user that installed Oracle Clusterware. Depending on whether you have a shared or nonshared Oracle home, complete one of the following procedures:

   • If you have a shared home, then run the following command from the Grid_home/oui/bin directory on the node you want to delete:

     $ ./runInstaller -detachHome  ORACLE_HOME=Grid_home
     

   • For a nonshared home, deinstall the Oracle Clusterware home from the node that you want to delete, as follows, by running the following command from the Grid_home/deinstall directory, where Grid_home is the path defined for the Oracle Clusterware home:

     $ ./deinstall –local
     

     Caution:

     If you do not specify the -local flag, then the command removes the grid infrastructure homes from every node in the cluster.

7. On any node other than the node you are deleting, run the following command from the Grid_home/oui/bin directory where remaining_nodes_list is a comma-delimited list of the nodes that are going to remain part of your cluster:

   $ ./runInstaller -updateNodeList ORACLE_HOME=Grid_home
   "CLUSTER_NODES={remaining_nodes_list}" CRS=TRUE
   

8. Run the following CVU command to verify that the specified nodes have been successfully deleted from the cluster:

   $ cluvfy stage -post nodedel -n node_list [-verbose]
   

   See Also:

   "cluvfy stage -post nodedel" for more information about this CVU command