Cloning an Oracle Clusterware 10.2 Setup

Enterprise Manager allows you to deploy one or more Oracle Clusterware 10.2 instances similar in configuration to a source instance.

Prerequisites for Cloning

Ensure that the following prerequisites are met before cloning:

You have setup the Grid Control properly to manage the source and target hosts.
You have a valid source Oracle home with read / write privileges.
You have a Central Agent (10.2 or above) monitoring all the destination hosts.
You have not installed Oracle Clusterware on the destination nodes.

Cloning to Form a New Cluster

To clone an Oracle Clusterware 10.2 Setup from installed Oracle homes to form a new cluster:

Select an Oracle Clusterware 10.2 home from the list of clonable homes and click Next.
At the Source Settings page, enter the working directory location, host credentials and the files to be excluded from the Oracle home archive. Ensure that Source is a clustered home option is selected by default. This option triggers cloning in clustered mode. Click Next.
The Product Settings page is rendered accordingly. Select Clone to a new cluster option and also ensure that the existing member nodes of the cluster have been appropriately populated. In the Destination Node Specification table, select the host names by clicking the icon and enter the public node name, private node names, and virtual IPs for each destination node. You need to provide these values as per /etc/hosts file. Click Next.
Provide the destination Oracle home information along with the destination host credentials. Ensure that the user name is identical in each host. Click Next.
Specify the pre/post/root scripts or commands to be executed before/after the cloning operation. The same script will be executed parallely in each destination. Oracle Clusterware root scripts and Oracle Clusterware post scripts will be executed serially. You may choose to execute pre/post scripts with sudo privileges, but the host credentials previously specified should have sudo privileges on the destination host for this to succeed. Failure of this step will not affect the overall status of the job. You may need to create a post script file with the following content and execute it:
- On UNIX:
%oracle_home%/oui/bin/runConfig.sh*ORACLE_HOME=%oracle_home% ACTION=clone MODE=perform
- On Windows:

OH/bin/racgons add_config node2:<remote_port> node3:<remote_port>

OH/bin/oifcfg setif -global <interface_name>/<subnet>:public <inteface_name>/<subnet>:cluster_interconnect [<interface_name>/<subnet>:public <inteface_name>/<subnet>:cluster_interconnect .......]

Click Next.

Review your selection and click Finish.

Cloning to Extend an Existing Cluster

To clone an Oracle Clusterware 10.2 Setup from installed Oracle homes to extend an existing cluster:

Select an Oracle Clusterware 10.2 home from the list of clonable homes and click Next.
At the Source Settings page, enter the working directory location, host credentials and the files to be excluded from the Oracle home archive. Ensure that Source is a clustered home option is selected by default. This option triggers cloning in clustered mode. Click Next.
The Product Settings page is rendered accordingly. Ensure that you select Extend the source cluster option and also ensure that the existing member nodes of the cluster have been appropriately populated. In the Destination Node Specification table, select the host names by clicking the icon and enter the public node name, private node names, and virtual IPs for each destination node. If you have already installed Oracle Clusterware on any host, you will get a warning for the same. Ensure that the Oracle home location and name is the same as the source. Click Next.
Provide the destination Oracle home information along with the destination host credentials. You need to ensure that these credentials are correct as they are not verified and the job may fail later if they are wrong. You must also ensure that the user name is identical in each host (user equivalence). Click Next.
Specify the pre/post/root scripts or commands to be executed before/after the cloning operation. Oracle Clusterware root scripts and Oracle Clusterware post scripts will be executed serially. You may choose to execute pre/post scripts with sudo privileges, but the host credentials previously specified should have sudo privileges on the destination host for this to succeed. Failure of this step will not affect the overall status of the job. You may need to create a post script file with the following content and execute it:
- On UNIX:
OH/bin/racgons add_config <host_name>:<remote_opmn_port>
- On Windows:

OH/bin/vipca -silent –addvips <node-name>/ip-name|ip-addr[,….] OH/bin/racgons add_config node2:<remote_port>

Click Next.

Note: When you execute root.sh script OH/install/rootaddnode.sh is automatically executed on the source home.

Imortant: If you do not have Sudo priviliges to execute the script as root, follow the instructions below to successfully execute root.sh.

Do not select Use Sudo in the Pre/Post Scripts page.

Submit the clone job to extend a cluster (for example, from a single node to two nodes).

Execute rootaddnode.sh (as root user) from node 1.

Execute root.sh from the cloned CRS Oracle home.

Review your selection and click Finish.

Related Topics

Enterprise Manager Information Roadmap