While Cloning the database through RMAN Duplicate, faced the below error
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 00/00/000 00:00:00
RMAN-05501: aborting duplication of target database
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time
CAUSE
The RMAN duplicate is executed with a target database connection.
A connection to target database is not allowed when using the "incarnation" keyword as stated in the Database Backup and Recovery Reference:
Duplication with a connection to a target does not support previous database incarnations.
However, you can specify previous incarnations if you are duplicating without a connection to a target database.
SOLUTION
Set the Database Incarnation back to an incarnation before the last RESETLOG time.
Example commands :
$ rman catalog rman/rman@rclone
RMAN> list incarnation;
set dbid <dbid before the resetlog time>
connect target un/pw@<alias>
reset database to incarnation 2;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 00/00/000 00:00:00
RMAN-05501: aborting duplication of target database
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time
CAUSE
The RMAN duplicate is executed with a target database connection.
A connection to target database is not allowed when using the "incarnation" keyword as stated in the Database Backup and Recovery Reference:
Duplication with a connection to a target does not support previous database incarnations.
However, you can specify previous incarnations if you are duplicating without a connection to a target database.
SOLUTION
Set the Database Incarnation back to an incarnation before the last RESETLOG time.
Example commands :
$ rman catalog rman/rman@rclone
RMAN> list incarnation;
set dbid <dbid before the resetlog time>
connect target un/pw@<alias>
reset database to incarnation 2;