Re: Changing DBID

From: joel garry <>
Date: Thu, 10 Jul 2008 11:32:50 -0700 (PDT)
Message-ID: <>

On Jul 10, 11:09 am, Chuck <> wrote:
> 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.

I'm wondering if this may answer your delete question, at least for the catalog: Also see unregister:

And a gentle reminder, it is often better to state what you are aiming for, as well as what you have tried, then just ask how to do something specific which may or may not be what you really want.


-- is bogus.
Received on Thu Jul 10 2008 - 13:32:50 CDT

Original text of this message