« Blogging Code of Ethics | Main | Introducing Sara Woodhull, Guest Author »

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.

References

Comments (6)

Steven Chan:

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

John Piwowar:

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. :)

suresh:

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.

Thanks
Suresh

Steven Chan:

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 

Uldis Augulis:

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.
.
Br
Uldis

Steven Chan:

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 

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

About This Entry

This page contains a single entry from the blog posted on April 4, 2007 2:18 PM.

The previous post in this blog was Blogging Code of Ethics.

The next post in this blog is Introducing Sara Woodhull, Guest Author.

Many more can be found on the main index page or by looking through the archives.

Archives

Subscribe to Updates

Powered by
Movable Type and Oracle