Generally speaking, my clones come from whichever backup suits our purpose (end of month close, etc.). In many cases, sites will have a monthly maintenance window that is used to perform the backups and to apply patches, etc. At that point, a cold backup is taken and is then used to refresh the lower instances ("QA", in particular). This cold backup may also be retained for audit/legal purposes for quite some time. While I tend to agree with your statements about testing recovery, etc., many shops do have the luxury of downtime to perform a cold backup. And, quite frankly, if I can have yet another backup process, I count myself lucky. It's also important to note that most shops don't have the luxury of using BCV's (or any other "snapshot" technology). (Although, quite frankly, I am a big fan of those tools). So, is there a benefit to cloning from a cold backup? Yes. Simplicity. Is it by any means necessary, of course not. Would I plan the shutdown/cold backup JUST to feed my clones? Of course not. But, if you have a cold backup to pull from, why not use it? -- James ---------------------------------------------------------------------- James J. Morrow | Senior Oracle Applications DBA | TriOra Group, LLC morrow.james <at> gmail <dot> com james.morrow <at> trioragroup <dot> com On Thu, Jun 11, 2009 at 7:51 AM, kathy.robb<kathy.robb@xxxxxxx> wrote: > I know some people do, but never ever is our answer, too. > > -----Original Message----- > From: ora-apps-dba-bounce@xxxxxxxxxxxxx > [mailto:ora-apps-dba-bounce@xxxxxxxxxxxxx] On Behalf Of Jurijs Velikanovs > Sent: Wednesday, June 10, 2009 11:52 PM > To: ora-apps-dba@xxxxxxxxxxxxx > Subject: How many of you do shutdown your EBS PROD to make a clone? > > Hi List, > > Just a quick question. Would you mind to at least answer YES or NO > (any comments are welcome). > Do you shutdown your EBS production database for cloning purposes? > > My answer is: Never! In fact I think it is an awful idea to shutdown > you production for cloning proposes for the following reasons: > 1. You introduce unnecessary downtime to a system users. You can use > hot backups instead. > 2. You miss a brilliant opportunity to test your recovery (including > recovery time regular assessment, and DBA training). > 3. You flush all you cache (shared and "buffer" pool). It will > slowdown your processes after you start you instance up. > On the other hand I don't see any benefits! > > PS I was told that even big EBS shops shutdown their systems to make > cold backups. Definitely not the systems that my team is responsible > for :) > > Yury > > > > > > >