Using Fleet Patching and Provisioning to Add a Node

If you have a Fleet Patching and Provisioning Server, then you can use Fleet Patching and Provisioning to add a node to a cluster with one command, as shown in the following example:

$ rhpctl addnode gihome -client rhpclient -newnodes clientnode2:clientnode2-vip -root

The preceding example adds a node named clientnode2 with VIP clientnode2-vip to the Fleet Patching and Provisioning Client named rhpclient, using root credentials (login for the node you are adding).

Using Oracle Grid Infrastructure Installer to Add a Node

To add a node to the cluster using the Oracle Grid Infrastructure installer

1. Run ./gridSetup.sh to start the installer.

2. On the Select Configuration Option page, select Add more nodes to the cluster.

3. On the Cluster Node Information page, click Add... to provide information for nodes you want to add.

4. When the verification process finishes on the Perform Prerequisite Checks page, check the summary and then click Install.

5. If prompted, then run the orainstRoot.sh script as root to populate the /etc/oraInst.loc file with the location of the central inventory. For example:

   # /opt/oracle/oraInventory/orainstRoot.sh

6. If you have an Oracle RAC or Oracle RAC One Node database configured on the cluster and you have a local Oracle home, then do the following to extend the Oracle database home to node3:

   1. Navigate to the Oracle_home/addnode directory on node1 and run the addnode.sh script as the user that installed Oracle RAC using the following syntax:

      $ ./addnode.sh "CLUSTER_NEW_NODES={node3}"

   2. Run the Oracle_home/root.sh script on node3 as root, where Oracle_home is the Oracle RAC home.

   3. Open the pluggable databases (PDBs) on the newly added node using the following commands in your SQL*Plus session:

      SQL> CONNECT / AS SYSDBA
      SQL> ALTER PLUGGABLE DATABASE pdb_name OPEN;

   If you have a shared Oracle home that is shared using Oracle Automatic Storage Management Cluster File System (Oracle ACFS), then do the following to extend the Oracle database home to node3:

   1. Run the Grid_home/root.sh script on node3 as root, where Grid_home is the Oracle Grid Infrastructure home.

   2. Run the following command as the user that installed Oracle RAC from the Oracle_home/oui/bin directory on the node you are adding to add the Oracle RAC database home:

      $ ./runInstaller -attachHome ORACLE_HOME="ORACLE_HOME" "CLUSTER_NODES={node3}"
      LOCAL_NODE="node3" ORACLE_HOME_NAME="home_name" -cfs

   3. Navigate to the Oracle_home/addnode directory on node1 and run the addnode.sh script as the user that installed Oracle RAC using the following syntax:

      $ ./addnode.sh -noCopy "CLUSTER_NEW_NODES={node3}"

      Note:

      Use the -noCopy option because the Oracle home on the destination node is already fully populated with software.

   If you have a shared Oracle home on a shared file system that is not Oracle ACFS, then you must first create a mount point for the Oracle RAC database home on the target node, mount and attach the Oracle RAC database home, and update the Oracle Inventory, as follows:

   1. Run the srvctl config database -db db_name command on an existing node in the cluster to obtain the mount point information.

   2. Run the following command as root on node3 to create the mount point:

      # mkdir -p mount_point_path

   3. Mount the file system that hosts the Oracle RAC database home.

   4. Run the following command as the user that installed Oracle RAC from the Oracle_home/oui/bin directory on the node you are adding to add the Oracle RAC database home:

      $ ./runInstaller -attachHome ORACLE_HOME="ORACLE_HOME" "CLUSTER
      _NODES={local_node_name}" LOCAL_NODE="node_name" ORACLE_HOME_NAME="home_name" -cfs

      Navigate to the Oracle_home/addnode directory on node1 and run the addnode.sh script as the user that installed Oracle RAC using the following syntax:

      $ ./addnode.sh -noCopy "CLUSTER_NEW_NODES={node3}"

      Note:

      Use the -noCopy option because the Oracle home on the destination node is already fully populated with software.

   Note:

   After running addnode.sh, ensure the Grid_home/network/admin/samples directory has permissions set to 750.

7. Run the Grid_home/root.sh script on the node3 as root and run the subsequent script, as instructed.

   Note:

   • If you ran the root.sh script in the previous step, then you do not need to run it again.

   • If you have a policy-managed database, then you must ensure that the Oracle home is cloned to the new node before you run the root.sh script.

   • If you have any administrator-managed database instances configured on the nodes which are going to be added to the cluster, then you must extend the Oracle home to the new node before you run the root.sh script.

     Alternatively, remove the administrator-managed database instances using the srvctl remove instance command.

8. Start the Oracle ACFS resource on the new node by running the following command as root from the Grid_home/bin directory:

   # srvctl start filesystem -device volume_device_name -node node3

   Note:

   Ensure the Oracle ACFS resources, including Oracle ACFS registry resource and Oracle ACFS file system resource where the Oracle home is located, are online on the newly added node.

9. Run the following CVU command as the user that installed Oracle Clusterware to check cluster integrity. This command verifies that any number of specified nodes has been successfully added to the cluster at the network, shared storage, and clusterware levels:

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

To delete a node from a cluster:

Using Fleet Patching and Provisioning to Delete a Node

Alternatively, you can use Fleet Patching and Provisioning to delete a node from a cluster with one command, as shown in the following example:

$ rhpctl deletenode gihome -client rhpclient -node clientnode2 -root

The preceding example deletes a node named clientnode2 from the Fleet Patching and Provisioning Client named rhpclient, using root credentials (login for the node you are deleting).

Ensure that you complete the prerequisites listed in "Prerequisite Steps for Adding Cluster Nodes" before adding nodes.

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

• There is an existing cluster with two nodes named node1 and node2

• You are adding a node named node3

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

To add a node:

1. Verify the integrity of the cluster and node3:

   C:\>cluvfy stage -pre nodeadd -n node3 [-fixup] [-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.

2. On node1, go to the Grid_home\addnode directory and run the addnode.bat script, as follows:

   C:\>addnode.bat "CLUSTER_NEW_NODES={node3}"
   "CLUSTER_NEW_VIRTUAL_HOSTNAMES={node3-vip}"

3. Run the following command on the new node:

   C:\>Grid_home\crs\config\gridconfig.bat

4. The following steps are required only if you have database homes configured to use Oracle ACFS:

   1. For each database configured to use Oracle ACFS, run the following command from the Oracle RAC database home:

      C:\>ORACLE_HOME/bin/srvctl stop database -db database_unique_name

      Note:

      Run the srvctl config database command to list all of the databases configured with Oracle Clusterware. Use the srvctl config database -db database_unique_name to find the database details. If the ORACLE_HOME path leads to the Oracle ACFS mount path, then the database uses Oracle ACFS. Use the command output to find the database instance name configured to run on the newly added node.

   2. Use Windows Server Manager Control to stop and delete services.

   3. For each of the databases and database homes collected in the first part of this step, run the following command:

      C:\> ORACLE_HOME/bin/srvctl start database -db database_unique_name

5. Run the following command to verify the integrity of the Oracle Clusterware components on all of the configured nodes, both the preexisting nodes and the nodes that you have added:

   C:\>cluvfy stage -post crsinst -n all [-verbose]

After you complete the procedure in this section for adding nodes, you can optionally extend Oracle Database with Oracle RAC components to the new nodes, making them members of an existing Oracle RAC database.

Creating the OraMTS Service for Microsoft Transaction Server

Oracle Services for Microsoft Transaction Server (OraMTS) permit Oracle databases to be used as resource managers in Microsoft application-coordinated transactions. OraMTS acts as a proxy for the Oracle database to the Microsoft Distributed Transaction Coordinator (MSDTC). As a result, OraMTS provides client-side connection pooling and allows client components that leverage Oracle to participate in promotable and distributed transactions. In addition, OraMTS can operate with Oracle databases running on any operating system, given that the services themselves are run on Windows.

On releases earlier than Oracle Database 12c, the OraMTS service was created as part of a software-only installation. Starting with Oracle Database 12c, you must use a configuration tool to create this service.

Create the OraMTS service after adding a node or performing a software-only installation for Oracle RAC, as follows:

1. Open a command window.

2. Change directories to %ORACLE_HOME%\bin.

3. Run the OraMTSCtl utility to create the OraMTS Service, where host_name is a list of nodes on which the service should be created:

   C:\..bin> oramtsctl.exe -new -host host_name

This procedure assumes that Oracle Clusterware is installed on node1, node2, and node3, and that you are deleting node3 from the cluster.

To delete a cluster node on Windows systems: