Database Backup and Recovery (MOSC)

MOSC Banner

Problem with incarnations of database in control file and rman catalog

edited Jun 15, 2011 5:45AM in Database Backup and Recovery (MOSC) 7 commentsAnswered
It looks like the incarnations are screwed up in one of our databases here are the incarnations from the control file

 List of Database Incarnations
DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
------- ------- -------- ---------------- --- ---------- ----------
1       1       PROD_CMS 3581960713       CURRENT 1          14-OCT-05
2       2       PROD_CMS 3581960713       PARENT  713210135  25-FEB-11

and in the rman catalog

List of Database Incarnations
DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
------- ------- -------- ---------------- --- ---------- ----------
26923   26925   PROD_CMS 3581960713       CURRENT 1          14-OCT-05
26923   26924   PROD_CMS 3581960713       ORPHAN  713210135  25-FEB-11

Obviously the control file is a little screwy as one would think the current and parent should be switched,  we tried running a sync between catalog and control file and it didn't resolve this at all.  What we are seeing though is strange .. RMAN backups are working fine, but its not purging any of the old backups even though we have it set to a retention time of 1 day, so we have been manually deleting and running cross checks..  so to fix this we plan on unregistering the database in rman,  creating the control file to trace with

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center