RMAN-20501
redo logs from parent database incarnation cannot be applied
Cause
A RESTORE or RECOVER of a data file was requested, but recovery of the data file would require applying redo logs that were generated before the most recent OPEN RESETLOGS.
Action
If a full backup or data file copy from the current database incarnation exists, ensure that it is marked AVAILABLE, and that a channel of the correct device type is allocated. It may also be necessary to remove the FROM BACKUPSET or FROM DATAFILECOPY or FROM TAG operands if these have been specified.
RMAN-20501
redo logs from parent database incarnation cannot be applied
Cause
A RESTORE or RECOVER of a data file was requested, but recovery of the data file would require applying redo logs that were generated before the most recent OPEN RESETLOGS.
Action
If a full backup or data file copy from the current database incarnation exists, ensure that it is marked AVAILABLE, and that a channel of the correct device type is allocated. It may also be necessary to remove the FROM BACKUPSET or FROM DATAFILECOPY or FROM TAG operands if these have been specified.
RMAN-20501
redo logs from parent database incarnation cannot be applied
Cause
A RESTORE or RECOVER of a data file was requested, but recovery of the data file would require applying redo logs that were generated before the most recent OPEN RESETLOGS.
Action
If a full backup or data file copy from the current database incarnation exists, ensure that it is marked AVAILABLE, and that a channel of the correct device type is allocated. It may also be necessary to remove the FROM BACKUPSET or FROM DATAFILECOPY or FROM TAG operands if these have been specified.
