Typical Cloning Deployment Scenario

Let us consider a typical cloning deployment scenario where we want to create a new Real Application Clusters setup with a single node and then extend that Real Application Clusters Setup to other nodes. We already have Node A that has the Oracle Clusterware home, Oracle Real Application Clusters home, and the Oracle ASM home. We create components of this home to the Software Library and create a single node (Node 1) Real Application Clusters setup. We extend this to other nodes Node 2 and Node 3.

Prerequisites

Ensure that the following prerequisites are met:

You already have a Real Application Clusters Oracle home installed.
You already have an Oracle Clusterware home installed.
You already have an ASM Oracle home installed.

Creating a Single Node Real Application Clusters Setup

To create a single node Real Application Clusters setup, perform the following steps:

Create the Oracle Clusterware Software Library Component by performing the following steps:
- From the Enterprise Manager Home page, click Deployments and then Provisoning sub-tab.
- In the Provisioning : Components page, click Create Component.
- Select the Oracle Clusterware Clone option from the drop-down list and click Next.
The Create Component : Configure page appears.
- Select the host name by clicking the icon and enter the home location, user name, password, working directory, and the files to be excluded and click Next.
The Create Component : Review Page appears.
- Review your selection and click Finish.

Create the Oracle Real Application Clusters Software Library Component and ASM Software Library Component by performing the following steps:
- From the Enterprise Manager Home page, click Deployments and then Provisoning sub-tab.
- In the Provisioning : Components page, click Create Component.
- Select the Oracle Database Clone option from the drop-down list and click Next.
The Create Component : Configure page appears.
- Select the host name by clicking the icon and enter the home location, user name, password, working directory, and the files to be excluded and click Next.
The Create Component : Review Page appears.
- Review your selection and click Finish.
You will have a setup similar to the figure below:
Clone from the Oracle Clusterware Software Library Component to a single node to create a single node cluster by following these steps:

Select the Oracle Clusterware Software Library Component and click Next .
At the Source Settings page, 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 node name by clicking the icon and enter the public node name. 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. 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.

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.

You will have a setup similar to the figure below:

Clone from the Oracle Real Application Clusters Software Library Component and clone it to the single node by following these steps:

Select the Oracle Real Application Clusters Software Library Component and click Next .

At the Source Settings page, 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 node name by clicking the icon and enter the public node name. 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.

You will have a setup similar to the figure below:

Clone a single instance database from a Gold Image to the single node by using the scripts or Database Configuration Assistant.

You will have a setup similar to the figure below:
Convert the single instance database to a Real Application Clusters Database by using the $ORACLE_HOME/bin/rconfig tool. This tool takes an XML input file and converts the single instance database using the information provided in the XML file. For more information, refer to Real Application Clusters Install Guide.

You will have a setup similar to the figure below:
Clone from the Oracle ASM Software Library Component (Oracle Database Component) and clone it to the single node by following these steps:
- Select the Oracle ASM Software Library Component and click Next .
- At the Source Settings page, 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 node name by clicking the icon and enter the public node name. 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.
You will have a setup similar to the figure below:
Configure the Real Application Clusters Database to use the ASM instance from the ASM home.

Now, we have a single node Real Application Cluster setup as shown in the figure below:

Extending a Real Application Clusters setup to one or two additional nodes

To extend the single node Real Application Clusters setup to one or two additional nodes, perform the following steps:

Clone from the Oracle Clusterware Software Library Component to extend the cluster to another two nodes by following these steps:
- Select the Oracle Clusterware Software Library Component and click Next.
- At the Source Settings page, 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. 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:
  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.

Review your selection and click Finish.

Clone from the Oracle Real Application Clusters Library Component to extend the cluster to another two nodes by following these steps:
- Select a Software Library home from the list of clonable homes and click Next.
- At the Source Settings page, 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 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.
Clone from the ASM Software Library Component to extend the cluster to another two nodes by following these steps:
- Select a Software Library home from the list of clonable homes and click Next.
- At the Source Settings page, 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 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.
Now, we have a Real Application Cluster setup with three nodes as shown in the figure below:
Go to the Admin tab, and click Add Instance to create the instances on the other two nodes that point to the same database file.

Related Topics

Enterprise Manager Information Roadmap