Re: Changing DBID
From: Chuck <chuckh1958_nospam_at_gmail.com>
Date: Thu, 10 Jul 2008 18:09:11 GMT
Message-ID: <bfsdk.1189$Ae3.328@trnddc05>
>
> That is a strange want, as you are saying you want to restore backups
> that cannot apply. If you are duping from another db, why do you
> think you should be able to use backups from before the dupe?
> Recovery is based on transactions. The transactional chain is broken
> as far as those backups are concerned.
Date: Thu, 10 Jul 2008 18:09:11 GMT
Message-ID: <bfsdk.1189$Ae3.328@trnddc05>
joel garry wrote:
>> Not the same as the source of the copy, but I want the destination of >> the copy to have the same DBID after the duplication as it had before.
>
> That is a strange want, as you are saying you want to restore backups
> that cannot apply. If you are duping from another db, why do you
> think you should be able to use backups from before the dupe?
> Recovery is based on transactions. The transactional chain is broken
> as far as those backups are concerned.
And why can't I apply them? Anything in the rman catalog can be restored even after a dupe. I'd just be restoring to a point in time before the dupe. As stated in an earlier posting in this thread, this is a TEST database and only gets cold backups. No recovery would be necessary.
In my specific case I have no intentions of ever restoring the old backups. I just want to delete them with a "delete obsolete" command. But since duplication changes the dbid, "delete obsolete" will not work on those pre-duplication backups and they sit forever in both the rman catalog and the MML. Received on Thu Jul 10 2008 - 13:09:11 CDT