Professional Documents
Culture Documents
So First About The Rapid Clone Method
So First About The Rapid Clone Method
Before starting I want to ask question. Why you need to do cloning ? Why we need to duplicate Oracle Application.
We need cloning for various of reasons. suppose I have got production instance and want to test some application. Now here I
want to test the application, need to apply some product specific patches which might affect whole application then I have to
give downtime which will affect business. So if I had the same this on whic hI can play and test my application or code or say I
can apply some patches and at the same time business also run then nothing like it. This can be achieved by cloning or
duplicating the application.
Duplicating the application is not easy or its just not simply copy the application, it wont work in any case. Logically it sounds
fine just to copy the filesystem and relink it and start the application but its not that easy.
Basically for cloning Oracle Application it can be categorised into three major categories.
You can achive first and third steps using a Rapid Clone utility which Oracle provides for cloning
There can be many ways and methods to clone Oracle Application which many organisations follows but the only supported
method provided by Oracle is using Rapid clone.
Rapid Clone is the new cloning utility introduced in Release 11.5.8. Rapid Clone leverages the new installation and
configuration technology utilized by Rapid Install.
Basically there are two cloning methodology using Autoconfig and without using autoconfig. First one that is using
autoconfig is completely replaced by Rapidclone.
Non-autocofig cloning methodology was generally used before 11.5.5 that is non autoconfig enabled system.
Here I will discuss Rapid Clone method of cloning and also throw some light on cloning 11.0.3 oracle application as some users
are still using that.
In Category 1 that is first you need to make source for clone. You need to dress up Source system so that only configuration
files and not the whole file system is copied.
Pre-requiste Steps
To start with cloning you need to first check about some pre-requisites some utilities should be of required version
After check ing the pre-requisites now your system is ready to clone.
After checking the above mentioned pre-requisites now you have to prepare the source system which need to be cloned.
In a broad way what this step will do is this will create the staged clone directory which will be having the driver files and
configuration file of the source.
So what exactly is going to happen in this step. Lets get in more details
Basically you have to run the adpreclone.pl script once for Application tier and one for the datbase (even if you are on single
node ! )
It will prepare datbase techstack at dbTechStack stage. Major activities it will take care of at this stage.
Now lets concentrate on Application tier side. Again it goes almost in the same way that is in two stages.
appltop preparation
APPL_TOP
OA_HTML ($COMMON_TOP/html)
JAVA_TOP
COMMON_TOP/util
COMMON_TOP/clone
8.0.6 ORACLE_HOME
iAS ORACLE_HOME
DB ORACLE_HOME
dbf files
After this stage now you need to configure the Target node. Basically you will run adcfgclone.pl same for databse tier and for
application tier.
Let go in bit more detail:
Stage at TechStack
-Creates context file for target adclonectx.pl
-Run driver files
$Oracle_806_Home/appsutil/driver/instconf.drv
$Oracle_iAS_Home/appsutil/driver/instconf.drv
So this will totally configure your application which has been copied.