Re: Testing Refresh Procedure

Kelley,

The process that is being used is sound and you know it works.

What a great opportunity for change! There is a wonderful chance to test your backup/recovery at the same time. This is a bit more complicated, so you might not want to do it every time. It also is dependent upon how the backups are being performed. There are also some 'gotchas', such as database links, hard coded connection strings, etc. that you need to work around.

I have used RMAN to refresh non-prod databases from production backups and it works incredibly well (as long as you remember the gotchas including changing the database id). I have also used non-RMAN backups to create these databases.

Regards,
Dan Fink

"Coleman, Kelley (HAC)" <Kelley.Coleman_at_va.gov> wrote: Does anyone have a standard procedure for doing db refreshes that they’d be willing to share? I’d be going from Production down to test and development dbs. These were usually done by a co-worker who recently moved on to greener pastures. He didn’t leave any desk procedures, so I’ve been winging it, but it seems like I’m making it harder than it needs to be.    

  Should I drop relevant schemas before importing, so it’s basically from scratch?    

  I know the pastures guy would essentially do two imports, one just of table structures – no rows – then one just of data. Does that seem like a sound procedure?   Kelley Coleman
 Database Administrator
 VA Health Administration Center
 Denver, Colorado
 303-331-7521-o  

 Confidentiality Note: This e-mail is intended only for the person or entity to which it is addressed, and may contain information that is privileged, confidential, or otherwise protected from disclosure. Dissemination, distribution, or copying of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this e-mail in error, please notify the sender by reply e-mail, phone, or fax, and destroy the original message and all copies. Thank you          

--
http://www.freelists.org/webpage/oracle-l