RMAN-20217: datafile not part of the database
Cause: The datafile does not exist or did not exist at until time/SCN. This is an internal error for restore database or tablespace.
Action: Check the datafile name or number. Contact Oracle Support Services.
RMAN-20216: backup piece is missing
Cause: This is an internal error.
Action: Contact Oracle Support Services.
RMAN-20215: backup set is missing
Cause: This is an internal error.
Action: Contact Oracle Support Services.
RMAN-20212: ambiguous proxy copy recid
Cause: This is an internal error.
Action: Contact Oracle Support Services.
RMAN-20211: FROM TIME is before RESETLOGS time
Cause: FROM TIME cannot be less than the database creation time or RESETLOGS time.
Action: Check the FROM TIME. If the database needs to be restored to an old incarnation, use the RESET DATABASE TO INCARNATION command.
RMAN-20210: invalid archived log range, thread number is null
Cause: This is an internal error.
Action: Contact Oracle Support Services.
RMAN-20209: duplicate datafile name
Cause: Two datafiles have the same name. This is an internal error.
Action: Contact Oracle Support Services.
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
Cause: UNTIL CHANGE cannot be less than the database RESETLOGS change.
Action: Check the UNTIL CHANGE. If the database needs to be restored to an old incarnation, use the RESET DATABASE TO INCARNATION command.
RMAN-20207: UNTIL TIME is before RESETLOGS time
Cause: UNTIL TIME cannot be less than the database creation time or RESETLOGS time.
Action: Check the UNTIL TIME. If the database needs to be restored to an old incarnation, use the RESET DATABASE TO INCARNATION command.
RMAN-20206: log sequence not found in the repository
Cause: The specified log sequence does not exists in log history of the current database incarnation.
Action: Check the THREAD and LOGSEQ. If the database needs to be recovered to a log sequence number before the current database incarnation, use RESET DATABASE TO INCARNATION command first.