You have to also change the DBID or else you now have two databases with
the same DBIDs but different SCNs.

As you ar finding out, that causes the RMAN recovery catalog to be
confused...

I know if you use RMAN to do the cloning, the DBID is changed as part of
the process, but there is (in 9.2) a utility DBNEWID available to change
the DBID.

Walt



Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.


From: Schleicher Jeremy D.
[mailto:oracledba-ezmlmshield-x45031053.[Email address protected]
Sent: Thursday, September 06, 2007 07:27
To: LazyDBA Discussion
Subject: RMAN question

I recently did a clone of one of my databases. Now when I list the
backups I get a RMAN-20011: target database incarnation is not current
in recovery catalog. However the clone is showing the backup images
from my target database. The question I have is if I do a reset
database from my original database will I loose the ability to restore
from the previous images that I used?



Jeremy Schleicher

ERP Database Administrator

Florida State University





---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY To post a
dba job: http://jobs.lazydba.com To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html

Oracle LazyDBA home page