10 Adding and Deleting Nodes and Instances on UNIX-Based Systems

Adding an Oracle Clusterware Home to a New Node Using OUI in Interactive Mode

1. Ensure that you have successfully installed Oracle Clusterware on at least one node in your cluster environment. To use these procedures as shown, your $CRS_HOME environment variable must identify your successfully installed Oracle Clusterware home.

2. Go to CRS_home/oui/bin and run the addNode.sh script.

3. The Oracle Universal Installer (OUI) displays the Node Selection Page on which you should select the node or nodes that you want to add and click Next.

4. Verify the entries that OUI displays on the Summary Page and click Next.

5. Run the rootaddNode.sh script from the CRS_home/install/ directory on the node from which you are running OUI.

6. Run the orainstRoot.sh script on the new node if OUI prompts you to do so.

   Note:

   The orainstRoot.sh script updates the contents of the oraInventory file on all of the nodes in a cluster. If your cluster's oraInventory file is stored in a shared directory, such as in a directory on a cluster file system, Oracle Database displays the following error when you run addnode.sh:

   SEVERE: Remote 'UpdateNodeList' failed on nodes: 'cpqshow2'.
    Refer to '/install/sana/orainv/logs/UpdateNode List2006-08-11
   _08-58-33AM.log' for details.
   

   If Oracle Database displays this error, run the following command to complete the update of the oraInventory file:

   /install/sana/rachome1/oui/bin/runInstaller -updateNodeList
    -noClusterEnabled ORACLE_HOME=/install/sana/rachome1 CLUSTER
   _NODES=cpqshow1,cpqshow2 CRS=false "INVENTORY
   _LOCATION=/install/sana/orainv" LOCAL_NODE=node_on_which_
   command_is_to_be_run
   

7. Run the root.sh script on the new node from CRS_home to start Oracle Clusterware on the new node.

8. Obtain the remote port identifier, which you need to know for the next step, by running the following command on the existing node from the CRS_home/opmn/conf directory:

   ocrdump -stdout -keyname DATABASE.ONS_HOSTS.host_name.PORT
   

9. From the CRS_home/bin directory on an existing node, run the Oracle Notification Service (RACGONS) utility as in the following example where remote_port is the port number from the previous step and node2 is the name of the node that you are adding:

   ./racgons add_config node2:remote_port
   

Adding an Oracle Clusterware Home to a New Node Using OUI in Silent Mode

1. Ensure that you have successfully installed Oracle Clusterware on at least one node in your cluster environment. To use these procedures as shown, your $CRS_HOME environment variable must identify your successfully installed Oracle Clusterware home.

2. Go to CRS_home/oui/bin and run the addNode.sh script using the following syntax where node2 is the name of the new node that you are adding, node2-priv is the private node name for the new node, and node2-vip is the VIP name for the new node:

   ./addNode.sh –silent "CLUSTER_NEW_NODES={node2}" 
   "CLUSTER_NEW_PRIVATE_NODE_NAMES={node2-priv}" 
   "CLUSTER_NEW_VIRTUAL_HOSTNAMES={node2-vip}" 
   

   Note:

   The addnode.sh script updates the contents of the oraInventory file on all of the nodes in a cluster. If your cluster's oraInventory file is stored in a shared directory, such as in a directory on a cluster file system, Oracle Database displays the following error when you run addnode.sh:

   SEVERE: Remote 'UpdateNodeList' failed on nodes: 'cpqshow2'.
    Refer to '/install/sana/orainv/logs/UpdateNode List2006-08-11
   _08-58-33AM.log' for details.
   

   If Oracle Database displays this error, run the following command to complete the update of the oraInventory file:

   /install/sana/rachome1/oui/bin/runInstaller -updateNodeList
    -noClusterEnabled ORACLE_HOME=/install/sana/rachome1 CLUSTER
   _NODES=cpqshow1,cpqshow2 CRS=false "INVENTORY
   _LOCATION=/install/sana/orainv" LOCAL_NODE=node_on_which_
   command_is_to_be_run
   

3. Perform OUI-related steps 5 through 9 from the previous section about using OUI interactively under the heading "Adding an Oracle Clusterware Home to a New Node Using OUI in Interactive Mode".

Adding an Oracle Home with Oracle RAC to a New Node Using OUI in Interactive Mode

1. Ensure that you have successfully installed Oracle with the Oracle RAC software on at least one node in your cluster environment. To use these procedures as shown, your $ORACLE_HOME environment variable must identify your successfully installed Oracle home.

2. Go to Oracle_home/oui/bin and run the addNode.sh script.

3. When OUI displays the Node Selection Page, select the node or nodes to be added and click Next.

4. Verify the entries that OUI displays on the Summary Page and click Next.

5. Run the root.sh script on the new node from Oracle_home when OUI prompts you to do so.

   Note:

   The root.sh script updates the contents of the oraInventory file on all of the nodes in a cluster. If your cluster's oraInventory file is stored in a shared directory, such as in a directory on a cluster file system, Oracle Database displays the following error when you run addnode.sh:

   SEVERE: Remote 'UpdateNodeList' failed on nodes: 'cpqshow2'.
    Refer to '/install/sana/orainv/logs/UpdateNode List2006-08-11
   _08-58-33AM.log' for details.
   

   If Oracle Database displays this error, run the following command on any one but only one of the nodes in the cluster to complete the update of the oraInventory file:

   /install/sana/rachome1/oui/bin/runInstaller -updateNodeList
    -noClusterEnabled ORACLE_HOME=/install/sana/rachome1 CLUSTER
   _NODES=cpqshow1,cpqshow2 CRS=false "INVENTORY
   _LOCATION=/install/sana/orainv" LOCAL_NODE=node_on_which_
   command_is_to_be_run
   

6. On the new node, run the Oracle Net Configuration Assistant (NETCA) as the Oracle RAC user to add a Listener.

7. Use the Enterprise Manager or DBCA to add an instance as described under the heading "Step 5: Adding Database Instances to New Nodes".

Adding an Oracle Home with Oracle RAC to a New Node Using OUI in Silent Mode

1. Ensure that you have successfully installed Oracle with the Oracle RAC software on at least one node in your cluster environment. To use these procedures, your $ORACLE_HOME environment variable must identify your successfully installed Oracle home and the node to be added is named node2.

2. Go to Oracle_home/oui/bin and run the addNode.sh script using the following syntax:

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

   Note:

   The addnode.sh script updates the contents of the oraInventory file on all of the nodes in a cluster. If your cluster's oraInventory file is stored in a shared directory, such as in a directory on a cluster file system, Oracle Database displays the following error when you run addnode.sh:

   SEVERE: Remote 'UpdateNodeList' failed on nodes: 'cpqshow2'.
    Refer to '/install/sana/orainv/logs/UpdateNode List2006-08-11
   _08-58-33AM.log' for details.
   

   If Oracle Database displays this error, run the following command on any one but only one of the nodes in the cluster to complete the update of the oraInventory file:

   /install/sana/rachome1/oui/bin/runInstaller -updateNodeList
    -noClusterEnabled ORACLE_HOME=/install/sana/rachome1 CLUSTER
   _NODES=cpqshow1,cpqshow2 CRS=false "INVENTORY
   _LOCATION=/install/sana/orainv" LOCAL_NODE=node_on_which_
   command_is_to_be_run
   

3. Perform steps 5 through 7 from the previous section about using OUI interactively under the heading "Adding an Oracle Home with Oracle RAC to a New Node Using OUI in Interactive Mode".

Deleting an Oracle Home with Oracle RAC Using OUI in Interactive Mode

1. From a node that is to remain a part of your Oracle RAC database environment, use Enterprise Manager or DBCA to remove any database instances from the node that you want to delete if instances exist on that node. To do this, refer to the procedure titled "Step 1: Deleting Instances from Oracle Real Application Clusters Databases".

2. If you use ASM and this is the home from which the ASM instance runs, then perform the ASM clean up procedures as described under "Step 3: ASM Instance Clean-Up Procedures for Node Deletion".

3. If this is the home from which the node-specific Listener runs, then use NETCA to remove the Listener and its Oracle Clusterware resources.

   See Also:

   Oracle Database Net Services Administrator's Guide for more information about NETCA

4. On the node to be deleted, ensure that the $ORACLE_HOME environment variable is set to the Oracle home, then run the following command only with a non-shared Oracle home from Oracle_home/oui/bin where node_name is the name of the node to be deleted:

   ./runInstaller -updateNodeList ORACLE_HOME=Oracle_home 
   "CLUSTER_NODES={node_name}" –local 
   

   For a non-shared home, on each node that you are deleting, run OUI from the home and deinstall this home. Make sure that you choose the home to be removed and not just the products under that home.

   Note:

   If the contents of the Oracle home are not completely removed, then remove the remaining contents of the Oracle home using the rm -rf ORACLE_HOME command, where ORACLE_HOME is the complete path to the Oracle home that you want to finish removing.

5. On the node to be deleted, ensure that the $ORACLE_HOME environment variable is defined for the shared home location and run the following command on each of the nodes that are to be deleted:

   ./runInstaller -detachHome -local ORACLE_HOME=Oracle_home
   

   For a non-shared home, on each node that you are deleting, ensure that the $ORACLE_HOME environment variable is defined for the home that you are deleting and run the following command:

   ./runInstaller -deinstall -silent "REMOVE_HOMES={Oracle_home}"
   

6. On any node other than the node that you are deleting, make sure that the $ORACLE_HOME environment variable is defined for the Oracle home that you are deleting. Run the following command from Oracle_home/oui/bin where remaining_nodes_list is a comma-delimited list of the nodes that are going to remain as part of your Oracle RAC database:

   ./runInstaller -updateNodeList ORACLE_HOME=Oracle_home 
   "CLUSTER_NODES={remaining_nodes_list}"
   

   When using a shared Oracle home, run the following version of the command:

   ./runInstaller -updateNodeList -noClusterEnabled ORACLE_HOME=CRS_home 
   "CLUSTER_NODES={remaining_nodes_list}" CRS=TRUE
   

Deleting an Oracle Home with Oracle RAC Using OUI in Silent Mode

1. Perform steps 1 through 4 from the previous section about using OUI interactively under the heading "Deleting an Oracle Home with Oracle RAC Using OUI in Interactive Mode".

2. Depending on whether you have a shared or non-shared Oracle home, complete one of the following two procedures:

   • For a shared home, ensure that the $ORACLE_HOME environment variable is defined for the shared home location and run the following command on each of the nodes that are to be deleted:

     ./runInstaller -detachHome -local ORACLE_HOME=Oracle_home
     

   • For a non-shared home, on each node that you are deleting, ensure that the $ORACLE_HOME environment variable is defined for the home that you are deleting and perform the following step:

     ./runInstaller -deinstall -silent "REMOVE_HOMES={Oracle_home}"
     

3. Perform Step 6 from the procedure, "Deleting an Oracle Home with Oracle RAC Using OUI in Interactive Mode".

Deleting an Oracle Clusterware Home Using OUI in Interactive Mode

1. Perform the delete node operation for database homes as described in the section titled "Deleting an Oracle Home with Oracle RAC Using OUI in Interactive Mode" or use the procedure, "Deleting an Oracle Home with Oracle RAC Using OUI in Silent Mode", and ensure that the $CRS_HOME environment variable is defined to identify the appropriate Oracle Clusterware home on each node.

2. If you ran the Oracle Interface Configuration Tool (OIFCFG) with the -global flag during the installation, then skip this step. Otherwise, from a node that is going to remain in your cluster, from the CRS_home/bin directory, run the following command where node2 is the name of the node that you are deleting:

   ./oifcfg delif –node node2
   

3. Obtain the remote port number, which you will use in the next step, using the following command from the CRS_home/bin directory:

   ocrdump -stdout -keyname DATABASE.ONS_HOSTS.host_name.PORT
   

4. From CRS_home/bin on a node that is going to remain in the cluster, run the Oracle Notification Service Utility (RACGONS) as in the following example where remote_port is the ONS remote port number that you obtained in the previous step and node2 is the name of the node that you are deleting:

   ./racgons remove_config node2:remote_port
   

5. On the node to be deleted, run rootdelete.sh as the root user from the CRS_home/install directory. If you are deleting more than one node, then perform this step on all of the other nodes that you are deleting.

6. From any node that you are not deleting, run the following command from the CRS_home/install directory as the root user where node2,node2-number represents the node and the node number that you want to delete:

   ./rootdeletenode.sh node2,node2-number
   

   If necessary, identify the node number using the following command on the node that you are deleting:

   CRS_home/bin/olsnodes -n
   

7. Perform this step only if your are using a non-shared Oracle home. On the node or nodes to be deleted, run the following command from the CRS_home/oui/bin directory where node_to_be_deleted is the name of the node that you are deleting:

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

8. Perform this step only if your are using a non-shared Oracle home. On the node that you are deleting, run OUI using the runInstaller command from the CRS_home/oui/bin directory to deinstall Oracle Clusterware.

   Deinstall the Oracle Clusterware home from the node that you are deleting using OUI as follows by running the following command from the Oracle_home/oui/bin directory, where CRS_home is the name defined for the Oracle Clusterware home:

   ./runInstaller -deinstall –silent "REMOVE_HOMES={CRS_home}"
   

9. If you are using a non-shared Oracle home, on any node other than the node that you are deleting, run the following command from the CRS_home/oui/bin directory where remaining_nodes_list is a comma-delimited list of the nodes that are going to remain part of your Oracle RAC database:

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

   If you are using a shared Oracle home, on any node other than the node that you are deleting, run the following command from the CRS_home/oui/bin directory where remaining_nodes_list is a comma-delimited list of the nodes that are going to remain part of your Oracle RAC database:

   ./runInstaller -updateNodeList -noClusterEnabled ORACLE_HOME=Oracle_home 
   "CLUSTER_NODES={remaining_nodes_list}"
   

Deleting an Oracle Clusterware Home Using OUI in Silent Mode

1. Perform steps 1 through 7 from the previous section about using OUI interactively under the heading "Deleting an Oracle Clusterware Home Using OUI in Interactive Mode". Also ensure that the $CRS_HOME environment variable is defined to identify the appropriate Oracle Clusterware home on each node.

2. Deinstall the Oracle Clusterware home from the node that you are deleting using OUI as follows by running the following command from the Oracle_home/oui/bin directory, where CRS_home is the name defined for the Oracle Clusterware home:

   ./runInstaller -deinstall –silent "REMOVE_HOMES={CRS_home}"
   

3. Perform step 9 from the previous section about using OUI interactively under the heading "Deleting an Oracle Clusterware Home Using OUI in Interactive Mode".

Step 1: Connecting New Nodes to the Cluster

Complete the following procedures to connect the new nodes to the cluster and to prepare them to support your Oracle RAC database:

• Making Physical Connections

• Installing the Operating System

• Creating Oracle Users

• Verifying the Installation with the Cluster Verification Utility

• Checking the Installation

Step 2: Extending Clusterware and Oracle Software to New Nodes

The following topics describe how to add new nodes to the clusterware and to the Oracle database software layers using OUI:

• Adding Nodes at the Vendor Clusterware Layer

• Adding Nodes at the Oracle Clusterware Layer

addNode.sh -silent "CLUSTER_NEW_NODES={nodeI, nodeI+1, … nodeI+n}" 
"CLUSTER_NEW_PRIVATE_NODE_NAMES={pnI, pnI+1, … pnI+n}" 
"CLUSTER_NEW_VIRTUAL_HOSTNAMES={vipI, vipI+1,…,vipI+n}"

addNode.sh -silent -responseFile filename OR addNode.bat -silent -responseFile filename

Step 3: Preparing Storage on New Nodes

To extend an existing Oracle RAC database to your new nodes, configure the shared storage for the new instances to be added on new nodes so that the storage type is the same as the storage that is already used by the existing nodes' instances. Prepare the same type of storage on the new nodes as you are using on the other nodes in the Oracle RAC environment that you want to extend as follows:

• Automatic Storage Management (ASM)

  If you are using ASM, then make sure that the new nodes can access the ASM disks with the same permissions as the existing nodes.

• Oracle Cluster File System (OCFS)

  If you are using Oracle Cluster File Systems, then make sure that the new nodes can access the cluster file systems in the same way that the other nodes access them.

• Vendor Cluster File Systems

  If your cluster database uses vendor cluster file systems, then configure the new nodes to use the vendor cluster file systems. Refer to the vendor clusterware documentation for the pre-installation steps for your UNIX platform.

• Raw Device Storage

  If your cluster database uses raw devices, then prepare the new raw devices by following the procedures described in the next section.

Run the following command to verify your cluster file system and obtain detailed output where nodelist includes both the pre-existing nodes and the newly added nodes and file system is the name of the file system that you used for the Oracle Cluster File System:

cluvfy comp cfs -n nodelist -f file system [-verbose]

cluvfy comp ssa [ -n node_list ] [ -s storageID_list ] [-verbose]

Step 4: Adding Nodes at the Oracle RAC Database Layer

To add nodes at the Oracle RAC database later, run OUI in add node mode to configure your new nodes. Before beginning this procedure, ensure that your existing nodes have the $ORACLE_HOME environment variable set correctly. If you have multiple Oracle homes, then perform the following steps for each Oracle home that you want to include on the new nodes:

1. On an existing node from the Oracle_home/oui/bin directory, run the addNode.sh script. This starts OUI in add node mode and displays the OUI Welcome page. Click Next on the Welcome page and OUI displays the Specify Cluster Nodes for Node Addition page.

   Note:

   The addnode.sh script updates the contents of the oraInventory file on all of the nodes in a cluster. If your cluster's oraInventory file is stored in a shared directory, such as in a directory on a cluster file system, Oracle Database displays the following error when you run addnode.sh:

   SEVERE: Remote 'UpdateNodeList' failed on nodes: 'cpqshow2'.
    Refer to '/install/sana/orainv/logs/UpdateNode List2006-08-11
   _08-58-33AM.log' for details.
   

   If Oracle Database displays this error, run the following command to complete the update of the oraInventory file:

   /install/sana/rachome1/oui/bin/runInstaller -updateNodeList
    -noClusterEnabled ORACLE_HOME=/install/sana/rachome1 CLUSTER
   _NODES=cpqshow1,cpqshow2 CRS=false "INVENTORY
   _LOCATION=/install/sana/orainv" LOCAL_NODE=node_on_which_
   command_is_to_be_run
   

2. The Specify Cluster Nodes for Node Addition page has a table showing the existing nodes associated with the Oracle home from which you launched OUI. A node selection table appears on the bottom of this page showing the nodes that are available for addition. Select the nodes that you want to add and click Next.

3. The OUI verifies connectivity and performs availability checks on the existing nodes and on the nodes that you want to add. Some of checks performed determine whether:

4. • The nodes are up

   • The nodes are accessible by way of the network

5. If any of the checks fail, then fix the problem and proceed or deselect the node that has the error and proceed. You cannot deselect existing nodes; you must correct problems on the existing nodes before proceeding with node addition. If all of the checks succeed, then OUI displays the Node Addition Summary page.

   Note:

   If any of the existing nodes are down, then perform the updateNodeList procedure on each of the nodes to fix the node list after the nodes are up. Run the following command where node_list is a comma-delimited list of all of the nodes on which Oracle RAC is deployed:

   oui/bin/runInstaller -updateNodeList 
   "CLUSTER_NODES={node_list}" -local
   

6. The Node Addition Summary page has the following information about the products that are installed in the Oracle home that you are going to extend to the new nodes:

   • The source for the add node process, which in this case is the Oracle home

   • The existing nodes and new nodes

   • The new nodes that you selected

   • The required and available space on the new nodes

   • The installed products listing all of the products that are already installed in the existing Oracle home

   Click Finish and OUI displays the Cluster Node Addition Progress page.

7. The Cluster Node Addition Progress page shows the status of the cluster node addition process. The table on this page has two columns showing the four phases of the node addition process and each phases' status as follows:

   • Copy the Oracle Home to the New Nodes: Copies the entire Oracle home from the local node to the new nodes unless the Oracle home is on a cluster file system

   • Save Cluster Inventory: Updates the node list associated with the Oracle home and its inventory

   • Run root.sh: Displays the dialog prompting you to run root.sh on the new nodes

   The Cluster Node Addition Progress page's Status column displays Succeeded if the phase completes, In Progress if the phase is in progress, and Suspended when the phase is pending execution. After OUI displays the End of Node Addition page, click Exit to end the OUI session.

8. Run the root.sh script on all of the new nodes.

   The Oracle Clusterware issues the oifcfg command as in the following example:

   oifcfg setif -global  eth0/146.56.76.0:public eth1/192.0.0.0:cluster_interconnect 
   

   This sets both networks to global. Therefore, you do not need to run the oifcfg command manually after you add a node unless the network interfaces differ.

9. For shared Oracle home users, run the following command only once on any of the nodes from the $ORACLE_HOME/oui/bin directory, where nodes_list is a comma-delimited list of the nodes that are part of your cluster:

   ./runInstaller -updateNodeList -noClusterEnabled ORACLE_HOME=Oracle_home
    CLUSTER_NODES=nodes_list
   

10. Add a Listener to the new node by running the Net Configuration Assistant (NetCA) from new node and selecting only the new node on the Node Selection page.

You can optionally run addNode.sh in silent mode, replacing steps 1 through 6, as follows where nodeI, nodeI+1, and so on are the new nodes that you are adding:

addNode.sh -silent "CLUSTER_NEW_NODES={nodeI, nodeI+1, … nodeI+n}" 

You can also specify the variable=value entries in a response file, known as filename, and you can run the addNode script as follows:

addNode.sh -silent -responseFile filename

After completing the procedures in this section, you have defined the new nodes at the cluster database layer. You can now add database instances to the new nodes as described in "Step 5: Adding Database Instances to New Nodes".

Step 5: Adding Database Instances to New Nodes

You can use Enterprise Manager, or the Database Configuration Assistant (DBCA) in either interactive mode or in silent mode, to add database instances to new nodes. Before beginning this procedure, ensure that your existing nodes have the $ORACLE_HOME environment variable set correctly. Use one of the following procedures to add the database instances to the new nodes:

• Using Enterprise Manager to Add Database Instances to New Nodes

• Using DBCA in Interactive Mode to Add Database Instances to New Nodes

• Using DBCA in Silent Mode to Add Database Instances to New Nodes

dbca -silent -addInstance -nodeList node -gdbName gdbname [-instanceName instname] -sysDBAUserName sysdba -sysDBAPassword password

Step 1: Deleting Instances from Oracle Real Application Clusters Databases

The procedures in this section explain how to use Enterprise Manager, or DBCA in interactive or silent mode, to delete an instance from an Oracle RAC database.

• Using Enterprise Manager to Delete Database Instances from Existing Nodes

• Using DBCA in Interactive Mode to Delete Database Instances from Existing Nodes

• Using DBCA in Silent Mode to Delete Instance from Existing Nodes

dbca -silent -deleteInstance [-nodeList node] -gdbName gdbname -instanceName instname -sysDBAUserName sysdba -sysDBAPassword password

Step 2: Deleting Nodes from Oracle Real Application Clusters Databases

Before beginning these procedures, ensure that your existing nodes have the $CRS_HOME and $ORACLE_HOME environment variables set correctly. Use the following procedures to delete nodes from Oracle clusters on UNIX-based systems:

1. If there are instances on the node that you want to delete, then perform the procedures in the section titled "Step 1: Deleting Instances from Oracle Real Application Clusters Databases" before executing these procedures. If you are deleting more than one node, then delete the instances from all the nodes that you are going to delete.

2. If you use ASM, then perform the procedures in the following section, "Step 3: ASM Instance Clean-Up Procedures for Node Deletion".

3. If this is the Oracle home from which the node-specific listener named LISTENER_nodename runs, then use NETCA to remove this listener. If necessary, re-create this listener in another home.

   See Also:

   Oracle Database Net Services Administrator's Guide for more information about NETCA

4. For a non-shared home, on each node that you are deleting, perform the following two steps:

   • Run the following command:

     runInstaller -updateNodeList ORACLE_HOME=Oracle_home
     "CLUSTER_NODES={node_to_be_deleted}" –local 
     

     The runInstaller command is located in the directory Oracle_home/oui/bin. Using this command does not launch an installer GUI.

   • Run OUI from the home and deinstall this home. Make sure that you choose the home to be removed and not just the products under that home.

5. If you are using a non-shared Oracle home, from an existing node, run the following command where node_list is a comma-delimited list of nodes that remain in the cluster:

   runInstaller -updateNodeList ORACLE_HOME=Oracle_home "CLUSTER_NODES={node_list}"
   

   If you are using a shared Oracle home, from an existing node, run the following command where node_list is a comma-delimited list of nodes that remain in the cluster:

   runInstaller -updateNodeList -noClusterEnabled ORACLE_HOME=Oracle_home 
   "CLUSTER_NODES={node_list}"
   

6. Run the following commands to remove node-specific interface configurations where nodename is the name of the node that you want to delete and remote_port is port on the deleted node:

   racgons remove_config nodename:remote_port
   oifcfg delif -node nodename
   

7. On the node that you are deleting, run the command CRS_home/install/rootdelete.sh to disable the Oracle Clusterware applications that are on the node. Only run this command once and use the nosharedhome argument if you are using a local file system. The default for this command is sharedhome which prevents you from updating the permissions of local files such that they can be removed by the oracle user.

   If the Oracle Cluster Registry (OCR) is on a shared path, then run the command CRS_home/install/rootdelete.sh remote sharedvar. If the ocr.loc file is not on a shared file system, then run the CRS_home/install/rootdelete.sh remote nosharedvar command.

   If you are deleting more than one node from your cluster, then repeat this step on each node that you are deleting.

8. Run CRS_home/install/rootdeletenode.sh on any remaining node in the cluster to delete the nodes from the Oracle cluster and to update OCR. If you are deleting multiple nodes, then run the command CRS_home/install/rootdeletenode.sh node1,node1-number,node2,node2-number,... nodeN,nodeN-number where node1 through nodeN is a list of the nodes that you want to delete, and node1-number through nodeN-number represents the node number. To determine the node number of any node, run the command CRS_home/bin/olsnodes -n. To delete only one node, enter the node name and number of the node that you want to delete with the command CRS_home/install/rootdeletenode.sh node1,node1-number.

9. For a non-shared Oracle home, on each node that you are deleting, perform the following two steps:

   • Run the following command:

     runInstaller -updateNodeList ORACLE_HOME=CRS_home
     CLUSTER_NODES="" –local CRS=true
     

     The runInstaller command is located in the CRS_home/oui/bin directory. Executing this command does not launch an installer GUI.

   • Run OUI from the home and deinstall this home. Make sure that you choose the home to be removed and not just the products under that home.

10. If using a non-shared Oracle home, from an existing node, run the following command:

    runInstaller -updateNodeList ORACLE_HOME=CRS_home 
    "CLUSTER_NODES={nodelist}"
    

    where nodelist is a comma-delimited list of nodes that remain in the cluster.

    For shared Oracle home users, run the following command on an existing node from the $ORACLE_HOME/oui/bin directory, where nodes_list is a comma-delimited list of the nodes that remain in your cluster:

    ./runInstaller -updateNodeList -noClusterEnabled ORACLE_HOME=CRS_home
     CLUSTER_NODES=nodes_list
    

11. Run the following command to verify that the node is no longer a member of the cluster and to verify that the Oracle Clusterware components have been removed from this node:

    cluvfy comp crs -n all [-verbose]
    

    The response from this command should not contain any information about the node that you deleted; the deleted node should no longer have the Oracle Clusterware components on it. This verifies that you have deleted the node from the cluster.

    See Also:

    "Using the Cluster Verification Utility" for more information about enabling and using the CVU

As mentioned earlier in this procedure, you can optionally delete nodes from Oracle Real Application Clusters databases in silent mode by completing the following steps:

1. Complete steps 1 through 3 of the procedure described at the start of this section under the heading "Step 2: Deleting Nodes from Oracle Real Application Clusters Databases".

2. Depending on whether you have a shared or non-shared Oracle home, complete one of the following two procedures:

   • For a shared home, run the following command on each of the nodes that are to be deleted:

     ./runInstaller -detachHome -local ORACLE_HOME=Oracle_home
     

   • For a non-shared home, on each node that you are deleting, perform the following two steps:

     • Run the following command:

       runInstaller -updateNodeList ORACLE_HOME=Oracle_home
       CLUSTER_NODES="" –local 
       

       The runInstaller command is located in the directory Oracle_home/oui/bin. Using this command does not launch an installer GUI.

     • Deinstall the Oracle home from the node that you are deleting by running the following command from the Oracle_home/oui/bin directory:

       ./runInstaller -deinstall -silent "REMOVE_HOMES={Oracle_home}"
       

3. Complete steps 5 through 10 from the procedure described in "Step 2: Deleting Nodes from Oracle Real Application Clusters Databases".

4. Depending on whether you have a shared or non-shared Oracle Clusterware home, complete one of the following two procedures:

   • For shared homes, do not perform a deinstall operation. Instead, perform a detach home operation on the node that you are deleting. To do this, run the following command from CRS_home/oui/bin:

     ./runInstaller -detachHome ORACLE_HOME=CRS_home
     

   • For a non-shared home, on each node that you are deleting, perform the following two steps:

     • Run the following command:

       runInstaller -updateNodeList ORACLE_HOME=CRS_home
       CLUSTER_NODES="" –local CRS=true
       

       The runInstaller command is located in the directory CRS_home/oui/bin. Executing this command does not launch an installer GUI.

     • On each node that you are deleting, perform the following step from the CRS_home/oui/bin directory:

       ./runInstaller -deinstall -silent "REMOVE_HOMES={CRS_home}"
       

       where CRS_home is the name given to the Oracle Clusterware home you are deleting.

5. Complete steps 10 and 11 of the procedure described at the start of this section.

Step 3: ASM Instance Clean-Up Procedures for Node Deletion

If you are using ASM, then perform the following procedure to remove the ASM instances:

1. Stop all of the databases that use the ASM instance that is running from the Oracle home that is on the node that you are deleting.

2. On the node that you are deleting, if this is the Oracle home which from which the ASM instance runs, then remove the ASM configuration by completing the following steps. Run the command srvctl stop asm -n node_name for all of the nodes on which this Oracle home exists. Run the command srvctl remove asm -n node for all nodes on which this Oracle home exists. If there are databases on this node that use ASM, then use DBCA Disk Group Management to create an ASM instance on one of the existing Oracle homes on the node, restart the databases if you stopped them.

3. If you are using a cluster file system for your ASM Oracle home, then ensure that your local node has the $ORACLE_BASE and $ORACLE_HOME environment variables set correctly. Run the following commands from a node other than the node that you are deleting, where node_number is the node number of the node that you are deleting:

   rm -r $ORACLE_BASE/admin/+ASM
   rm -f $ORACLE_HOME/dbs/*ASMnode_number
   

   Note:

   You can identify the node number of the node that you want to delete by running the command CRS_home/bin/olsnodes -n node on the node that you are deleting.

4. If you are not using a cluster file system for your ASM Oracle home, then run the rm or delete commands mentioned in the previous step on each node on which the Oracle home exists.