Re: Interesting RMAN duplicate problem.
From: Niall Litchfield <niall.litchfield_at_gmail.com>
Date: Wed, 27 Jan 2010 10:52:14 +0000
Message-ID: <7765c8971001270252m5d52fc24n28d260df620bf9ea_at_mail.gmail.com>
On Wed, Jan 27, 2010 at 10:40 AM, Dunbar, Norman < norman.dunbar_at_environment-agency.gov.uk> wrote:
Date: Wed, 27 Jan 2010 10:52:14 +0000
Message-ID: <7765c8971001270252m5d52fc24n28d260df620bf9ea_at_mail.gmail.com>
On Wed, Jan 27, 2010 at 10:40 AM, Dunbar, Norman < norman.dunbar_at_environment-agency.gov.uk> wrote:
> I use the term "interesting" in the subject line loosely!
A courageous decision Minister! er anyway now I've got that out of my system for today.
You won't be able to recover the db beyond the first missing archive log. You should however be able to recover up to that point. I wouldn't be using the RMAN clone feature in this circumstance, but do an incomplete recovery using RMAN and then use good ole NID to change the dbname and id.
-- Niall Litchfield Oracle DBA http://www.orawin.info -- http://www.freelists.org/webpage/oracle-lReceived on Wed Jan 27 2010 - 04:52:14 CST