Steps involved in Cloned Target System in R12 EBS Enviornment

1. Prepare the Source system database and application Tier for cloning.

2. Copy the Source System to Target System

3. Configure the Target System

4. Post Clone Tasks.

Steps involved in Adding a Node using Advance Cloning Options in R12 EBS

In this post I am going discuss steps involved in Adding a Node using Advance Cloning Options in R12 EBS


1. Rapid Clone can be used to setup a new node being added to an existing application system.

2. On your new node can either run the Same services as the source node or different services.

3. Prepare the Source system, copy it to the new node and configure it as applicable.

4. Once the adcfgclone.pl completes, set up the environment and run adaddnode.pl on the target system.

cd $COMMON_TOP/clone/bin

perl adaddnode.pl

Steps Involved in Cloning for Mulit-Node Systems in R12 EBS Enviornment

I am going discuss in this post Steps involved in Cloning Mulit-Node Systems in R12 EBS environemnt. Rapid clone also used for Mulit-Node System cloning like Single-Node System.

In R12 Release,only one copy of the files for the application tier nodes needs to be copied to the target system as new feature of unified APPL_TOP introduced. In which all files required for all application tier services are included with every applications node, with multiple nodes being differentitated by the services started on each.You can clone using shared file system too.You can specify the services to start for each target node while entering response to the prompts during configuration steps.

To add non-shared applications nodes,carry out the copy and configure steps in the same way as on Primary Node.

Clone a Single-Node System to Mulit-Node System

This method of cloning allows the original node system to be cloned into a multi-node system.

Pre-Steps on the source and all target nodes.

a. Verify source and target node software versions
b. Apply the latest Rapid Clone patch (if required or applicable)
c. Set up Rapid Clone on the Apps Tier.
d. Set up Rapid Clone on the DB Tier.

Steps involved in Cloning procedure


a. Prepare the source system
b. Copy the Source system to the Target System
c. Configure the Target System
d. Post clone Steps like Profile update,utl_file_dir,Printer update, Workflow mailer etc.

Cloning a Mulit-Node System to a Mulit-Node System

1. A multi-node system can be cloned if the number of nodes and distribution of servers inthe target system matches that of the source system.

2. To clone a multi-node system to multi-node system perform the cloning process on each node.

Special Note: Always cloned database instance first.

Steps involved in Refreshing a Target System in R12 EBS Environment

In this post I am going to discuss about Refresh a Target System in R12 E-Business Suite environment.

The system to be clone is called as "Source System" and newly created(or cloned) system is called as "Target System".

Step 1: Ref in my previous post "Steps Involved in Cloning R12 e-Business Suites Environment (Single Node)" to prepare the source system.

Step 2: Copy any parts of the application tier file system that have been updated on the source system. It may require to refresh the target system's APPL_TOP,COMMON_TOP,or Tech Stack.

Step 3: You need to Refresh your database node at the same time. For database node refresh, Copy the database node file system ($ORACLE_HOME - RDBMS HOME).

Step 4: To configure the Target System to be Refreshed by specifying the exisiting Target System when running adcfgclone.pl.

perl adcfgclone.pl dbTier <CONTEXT FILE ON TARGET SYSTEM ON DATABASE NODE>

perl adcfgclone.pl appsTier <$INST_TOP/appl/admin/<CONTEXT FILE ON TARGET SYSTEM ON APPS TIER>>

Step 5: Once Refresh is finished. If you have customized environment then change post clone profile options, utl_file_dir etc.


Test your Refreshed environment and enter the below URL in your browser

http://r12b.quickoracle.com:8000

or

http://<hostname>.<domain_name>:<HTTP port>