Cloning a Real Application Clusters 10.1 Setup from Installed Oracle Homes

Enterprise Manager allows you to deploy one or more Real Application Clusters 10.1 instances similar in configuration to a source instance, either to form a new cluster or to extend an existing cluster.

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 Oracle Clusterware already installed on the destination nodes.
You must have all destination nodes on the same Oracle Clusterware cluster for a successful Real Application Clusters setup.

Cloning to Form a New Cluster

To clone a Real Application Clusters 10.1 setup from installed Oracle homes to form a new cluster:

Select an Oracle 10.1 Database Oracle 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 Clone to a new cluster option is selected and enter the new Oracle home location and name. In the Destination Node Specification table, select the host names by clicking the icon and enter the public node name for the destination node. If Oracle Clusterware is not installed on any host or the destination nodes do not belong to the same cluster, you will be warned of the same. Click Next.
Provide the destination host credentials and the working directory location. Ensure that these credentials are correct as these are not verified here and the job may fail later if these are wrong. 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 on each destination. 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. Click Next.
Note: If root.sh is not running through the job, you must run it manually for the cloning operation to complete.
Schedule the job immediately or at an appropriate time. You can also change the name of the job, from the default one that uses the time stamp. Click Next.
Review your selection and click Finish.

Cloning to Extend an Existing Cluster

To clone a Real Application Clusters 10.1 setup from installed Oracle homes to extend an existing cluster:

Select an Oracle 10.1 Database Oracle 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 for the destination node. If Oracle Clusterware is not installed on any host or the destination nodes do not belong to the same cluster, you will be warned of the same. Click Next.
Provide the destination host credentials and the working directory location. Ensure that these credentials are correct as these are not verified here and the job may fail later if these are wrong. Click Next.

Note: When you extend a source cluster, the destination Oracle home location and Oracle home name will be the same as the source.

Specify the pre/post/root scripts or commands to be executed before/after the cloning operation. The same script will be executed parallely on each destination. 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. Click Next.

Note: If root.sh is not run through the job, you must run it manually for the cloning operation to complete.

Schedule the job immediately or at an appropriate time. You can also change the name of the job, from the default one that uses the time stamp. Click Next.
Review your selection and click Finish.

Related Topics

Cloning RAC

Enterprise Manager Information Roadmap