Category Archives: RMAN Database Error Messages

RMAN-20504: corruption list not found in recovery catalog

oracle

RMAN-20504: corruption list not found in recovery catalog
Cause: The corruption list is empty.
Action: Make sure that one or more blocks are marked corrupt in V$COPY_CORRUPTION and V$BACKUP_CORRUPTION, and that the recovery catalog is up-to-date.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

RMAN-20504: corruption list not found in recovery catalog

oracle

RMAN-20504: corruption list not found in recovery catalog
Cause: The corruption list is empty.
Action: Make sure that one or more blocks are marked corrupt in V$COPY_CORRUPTION and V$BACKUP_CORRUPTION, and that the recovery catalog is up-to-date.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

RMAN-20503: DELETE cannot delete expired objects – run CROSSCHECK or DELETE EXPIRED

oracle

RMAN-20503: DELETE cannot delete expired objects - run CROSSCHECK or DELETE EXPIRED
Cause: A DELETE command was run without the EXPIRED option, but the object doesn't exist. This means the recovery catalog or controlfile is out of sync.
Action: Run CROSSCHECK.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

RMAN-20502: DELETE EXPIRED cannot delete objects that exist – run CROSSCHECK

oracle

RMAN-20502: DELETE EXPIRED cannot delete objects that exist - run CROSSCHECK
Cause: A DELETE EXPIRED command was run, but the object was actually found to exist. This means the recovery catalog or controlfile is out of sync.
Action: Run CROSSCHECK.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

RMAN-20501: redo logs from parent database incarnation cannot be applied

oracle

RMAN-20501: redo logs from parent database incarnation cannot be applied
Cause: A RESTORE or RECOVER of a datafile was requested, but recovery of the datafile would require applying redo logs that were generated before the most recent OPEN RESETLOGS.
Action: If a full backup or datafilecopy from the current database incarnation exists, then 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, FROM DATAFILECOPY, or FROM TAG operands if these have been specified.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

RMAN-20500: media recovery aborted

oracle

RMAN-20500: media recovery aborted
Cause:
Action:

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

RMAN-20401: script already exists

oracle

RMAN-20401: script already exists
Cause: A CREATE SCRIPT was issued, but a script with the specified name already exists.
Action: Use a different name or use REPLACE SCRIPT.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

RMAN-20400: stored script not found

oracle

RMAN-20400: stored script not found
Cause: A CREATE SCRIPT or DELETE SCRIPT specified a script name that could not be found.
Action: Check the script name.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

RMAN-20311: ambiguous proxy copy handle

oracle

RMAN-20311: ambiguous proxy copy handle
Cause: More than one proxy copy in the recovery catalog matches the specified handle.
Action: Use the proxy copy key to uniquely specify the proxy copy.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

RMAN-20310: proxy copy not found in the recovery catalog

oracle

RMAN-20310: proxy copy not found in the recovery catalog
Cause: The specified proxy copy is not in the recovery catalog or it has been marked deleted.
Action: Check the proxy copy handle or key.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/