If you are performing a SCN or time based recovery and RMAN-20208 is returned, It means that there was a SCN or time-based recovery previously done after which database was opened with reset logs, and now database has a new incarnation number. If you once again want to perform a recovery for any reason, or previously done incomplete recovery was not until the point where we wanted database to be, you need to reset the incarnation of the database and repeat the incomplete recovery process.
Following is how error is returned, and how to reset the incarnation number to the previous value for recovery process to succeed.RMAN> run{ set until scn 8686596; restore database; recover database; }
executing command: SET until clause
Starting restore at 19-MAY-23 using target database control file instead of recovery catalog RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of restore command at 05/19/2023 03:57:52 RMAN-20208: UNTIL CHANGE is before RESETLOGS change |
Resetting Database Incarnation Number
RMAN> list incarnation ;
using target database control file instead of recovery catalog
List of Database Incarnations DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time ------- ------- -------- ---------------- --- ---------- -------------------------------------------------- 1 1 PRODDB1 3643226197 PARENT 1 17-OCT-22 2 2 PRODDB1 3643226197 PARENT 1564562 17-FEB-23 3 3 PRODDB1 3643226197 CURRENT 8940723 18-MAY-23
RMAN> reset database to incarnation 2;
database reset to incarnation 2
RMAN> list incarnation;
List of Database Incarnations DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time ------- ------- -------- ---------------- --- ---------- -------------------------------------------------- 1 1 PRODDB1 3643226197 PARENT 1 17-OCT-22 2 2 PRODDB1 3643226197 CURRENT 1564562 17-FEB-23 3 3 PRODDB1 3643226197 ORPHAN 8940723 18-MAY-23 |
No comments:
Post a Comment