Fully Automated Cloning for Release 11i and 12

Cloning is the process of creating an identical copy of an already existing Oracle Applications system.  Cloning is a regular part of an Apps DBA's responsibilities, so you're probably already familiar with the latest Rapid Clone utility and its predecessor,  adclone.pl, the original AD Clone Utility.  If you've used those tools in the past, you likely also know that overall cloning process requires some user intervention for things like the APPS password and so on. 

Enterprise Manager Screenshot:

A customer recently asked whether the following cloning process can be fully automated, so that no user intervention is required at all:
  1. Shut down the PROD environment for both the application server and database tier
  2. Do an offline preclone of both tiers
  3. Copy both tiers to another server (the sandbox environment)
  4. Restart the PROD environment
  5. Do an offline postclone of both tiers for the sandbox environment
  6. Start the sandbox environment
In researching that, I was pleased to learn that this kind of automation is a new feature in the latest Application Management Pack for Oracle E-Business Suite for Enterprise Manager Grid Control 10gR3. 

The management pack automates the cloning of both Release 11i (11.5.10 with ATG RUP4) as well as Release 12 environments.  You go through a step-by-step interview process to configure the clone routine once, and then you can reuse the cloning routine as many times as you wish.  In addition, the cloning routing can send out a notification if it failed.

Very slick.  If you've had a chance to try this, I'd be interested in hearing about your experiences with this new feature.



Hi, John,The out-of-the-box cloning capabilities of the Apps Management Pack use the standard Rapid Clone utility.  Rapid Clone itself requires the E-Business Suite environment be brought down before the extraction process (the process that grabs data from the Source system) begins.  The Application Management Pack affords enough flexibility and
customization options that you can hook your own steps into the cloning
process.  If customers have their own cloning tools or scripts that support hot cloning, those can be hooked into a customized process and automated by the Application Management pack.  Regards,Steven

Posted by Steven Chan on April 05, 2007 at 05:02 AM PDT #

Hi Steven,

While this feature certainly is cool in principle, if it really requires a shutdown of the production instance, I question its practical value. I can't see incurring the downtime just so I can avoid a couple of manual intervention steps.

Or are steps 1) and 4) part of the customers' requirements, not a limitation the Apps Management Pack feature? If the management pack can handle fully automated "hot" cloning, then I might be pestering my manager to find room in the budget for Apps Management Pack licenses. :)

Posted by John Piwowar on April 05, 2007 at 06:33 AM PDT #

Hi Steven

I dont see a formal document talking about cloning when ASM is involved for DB Tier. Can you point me to any metalink doc available.


Posted by suresh on May 21, 2007 at 07:10 AM PDT #

Hi, Suresh,I know that the cloning-related documentation for RAC/ASM for Release 12 environments is still being worked on right now.  I'm trying to get confirmation of our plans for 11i documentation, too.  I'll post pointers to that information when I get my hands on it.Regards,Steven 

Posted by Steven Chan on May 25, 2007 at 07:34 AM PDT #

Hi Steven,
I tried out cloning possibilities through OAM on R12 as well as on 11i and have to admit that at this moment solution is unsteady.
I was not able to clone R12 since custom s_tools_oh , s_at and s_weboh_oh is not supported. Only manual way with parse file works for R12. As far as I know RUP4 will address this issue.
Besides that there are problems with file permissions in stage area and problems with automatic responses (for example see Note:412044.1 for tracking bugs 5741411 and 6044708)
I am really looking forward to try out Apps Management Pack with roll-up patch 2.0.1 since idea of cloning automation out of box is quite good.
Would appreciate if You share more info about others experience with cloning 11i and R12 through OEM.

Posted by Uldis Augulis on November 28, 2007 at 07:48 PM PST #

Hi, Uldis,I don't have a lot of visibility into customers' experiences with OEM, but I'd be happy to pass your feedback on to that team.  If you have specific Service Request numbers that have more details about the issues you've noted, I can pass those along, too.Regards,Steven 

Posted by Steven Chan on November 29, 2007 at 04:28 AM PST #


Do we need to rename directories in target node which contains host system's SID and HOSTnames ?

Is there any utility for doing that task ..


Posted by Ram on July 21, 2008 at 05:42 PM PDT #

Hello Ram,

For 11i, you do not need to explicitly rename these directories as new ones are created for the target node SID and HOST. Although the clone does some tidying up, the original source node directories will still exist but can be manually removed if required (or just ignored otherwise).

With R12, there is no need to copy $INST_TOP so will not have the source system directories on the target node and the clone will create the target system directories as needed



Posted by Mike Shaw on July 21, 2008 at 09:47 PM PDT #


On this year HROUG (Croatian Oracle Users group) I will have workshop with name "One click clone" (http://www.hroug.hr/hr/hroug_konferencija/u_pripremi/hroug2008_rovinj/predavanja_radionice_demogroundi/radionice/one_click_clone).

I will show how fully automated clonning of Oracle EBS On Linux RH4 is performed without shutting down nor database nor application part.

Scripts will be public on that site after the conference. I invite all of interested to visit it or to contact me on funky_disco_freak@yahoo.com.


Damir Vadas

Posted by Damir Vadas on September 09, 2008 at 01:36 AM PDT #

How to share these scripts here with other Oracle APPS DBA?

Posted by Damir Vadas on October 09, 2008 at 09:02 PM PDT #

Hi, Damir,

I can't post your scripts on my blog, but you're welcome to upload them to the public file-sharing site of your choice and then announce their availability here:

OTN "Managing Oracle Applications" forum


Posted by Steven Chan on October 10, 2008 at 04:52 AM PDT #

THX for suggestion.

Looking forward for comments...

Posted by Damir Vadas on October 10, 2008 at 09:39 AM PDT #

How to share these scripts here with other Oracle APPS DBA?
tuyen dung | viec lam | tim viec

Posted by nhat truong on August 18, 2009 at 06:11 PM PDT #


Damir has shared his scripts in the link shown in his Oct 10, 2008 comment above.


Posted by Steven Chan on August 19, 2009 at 04:55 AM PDT #

I have this cloning problem relate to Rapid clone merged and open this service request: 3-1096421101.
But it seems like there is no answer from Oracle support on this. Seem like they don't have any solution even after many tries. Would you be able to help?


Posted by Tan Do on December 11, 2009 at 02:07 AM PST #

Hi, Tan,

I'm sorry to hear that you're having trouble with this. I've just taken a look at your SR. It appears that the Support engineer has made an additional suggestion yesterday and is waiting for your reply.

I've also connected the Support engineer with one of our senior cloning architects in Development, in case there's something that requires Development involvement here.

Good luck with your SR.


Posted by Steven Chan on December 11, 2009 at 05:52 AM PST #


Is there any recent information about automated cloning? We have been on 12.1.3 for about 18 months and now the business wants a full refresh of the Support environment every week. Is a clone the best way to go?

My DBAs say it takes 2 days. Does that sound right?

Thank you,

Posted by Stuart on July 16, 2015 at 07:30 PM PDT #

Stuart, since the posting of this article there have been many changes and additions in the Application Management Suite Cloning feature. You may want to look at the latest version.

Posted by Max Arderius on July 17, 2015 at 07:09 AM PDT #

Post a Comment:
Comments are closed for this entry.


« June 2016