Skip Headers
Oracle® Real Application Clusters Administration and Deployment Guide
11g Release 1 (11.1)

Part Number B28254-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

8 Using Cloning to Extend Oracle RAC to Nodes in the Same Cluster

This chapter provides information about using cloning to extend Oracle Real Application Clusters (Oracle RAC) to additional nodes in an existing cluster. To add ASM and Oracle RAC to nodes in a new cluster, see Chapter 7.

See Also:

"Introduction to Cloning Oracle ASM and Oracle RAC" for an overview of cloning and a discussion about the benefits of cloning

Adding Nodes Using Cloning in Oracle Real Application Clusters Environments

This section explains how to add nodes to existing Oracle RAC environments by using Oracle cloning for Linux and UNIX system environments.

The cloning procedures assume that you have successfully installed and configured an Oracle RAC environment to which you want to add nodes and instances. To add nodes to an Oracle RAC environment using cloning, first extend the Oracle Clusterware configuration, then extend the Oracle Database software with Oracle RAC, and then add the listeners and instances by running the Oracle assistants

Complete the following steps to clone Oracle Database with Oracle RAC software on Linux and UNIX systems:

  1. Follow the steps in the "Preparing to Clone ASM and Oracle RAC" to create a copy of an Oracle home that you then use to perform the cloning procedure on one or more nodes.

  2. If you do not have a shared Oracle Database home, then tar the Oracle home from the existing node and copy it to the new node. Assume that the location of the destination Oracle home on the new node is $ORACLE_HOME. Otherwise, skip this step.

  3. If you do not have a shared Oracle Database home, then on the new node go to the $ORACLE_HOME/clone/bin directory and run the following command where existing_node is the name of the node that you are cloning, new_node2 and new_node3 are the names of the new nodes, and Oracle_home_name is the name of the Oracle home:

    perl clone.pl '-O"CLUSTER_NODES={existing_node,new_node2,new_node3}"'
     '-O"LOCAL_NODE=new_node2"' ORACLE_BASE=/opt/oracle ORACLE_HOME=$ORACLE_HOME
     ORACLE_HOME_NAME=Oracle_home_name '-O-noConfig' 
    

    If you have a shared Oracle Database home, then append the -cfs option to the command example in this step for the cluster file system:

    perl clone.pl '-OÒCLUSTER_NODES={existing_node,new_node2,new_node3}"'
    '-O"LOCAL_NODE=new_node2"' ORACLE_BASE=/opt/oracle ORACLE_HOME=$ORACLE_HOME
     ORACLE_HOME_NAME=Oracle_home_name '-O-noConfig'  '-O-cfs'
    
  4. Run the following command on the existing node from the $ORACLE_HOME/oui/bin directory where existing_node is the name of the original node that you are cloning and new_node2 and new_node3 are the names of the new node:

    ./runInstaller –updateNodeList ORACLE_HOME=$ORACLE_HOME "CLUSTER_
    NODES={existing_node,new_node2,new_node3}" 
    
  5. On the new node, go to the $ORACLE_HOME directory and run the following command:

    ./root.sh
    
  6. On the new node, run Net Configuration Assistant (NETCA) to add a listener.

  7. From the node that you cloned, run Database Configuration Assistant (DBCA) to add the new instance.

The cloning script runs multiple tools, each of which may generate its own log files. After the clone.pl script finishes running, you can view log files to obtain more information about the cloning process. See "Locating and Viewing Log Files Generated During Cloning" for more information.

When cloning the Oracle Database with Oracle RAC: