Cry about...
Oracle Troubleshooting

RMAN-06089: archive log XXX not found or out of sync with catalog


RMAN80 generates the error:

RMAN-06089: archive log XXX not found or out of sync with catalog


This error indicates that the named file is not found or is found but is not the same file that the recovery catalogue thinks it is.

Possible Remedies:

  • If the archivelog file has been renamed then rename it back to what the recovery manager (RMAN) expects. This may occur if the archive log name format is changed.
  • If using a recovery catalogue then re-catalogue the file and retry the operation. To re-catalog archive logs issue the commands:

    rman80 target internal
    > Reset database;

    This cannot be used if no recovery catalogue is being used.

  • If not using a recovery catalogue then the only way to resolve this problem is to reset the logs:
    Connect internal
    Startup mount
    Recover database until cancel using backup controlfile;
    Alter database open resetlogs;

    Be aware that because this resets the logs, it will no longer be possible to apply any newly generated archive logs to the last full backup to restore the database. Accordingly, be sure to take a new full backup of the database as soon as possible.

These notes have been tested with Oracle 8.0.5 running on Window NT 4.

This page represents one page of many pages of notes I made whilst working with Oracle 7 through to 10i. I now no longer work with Oracle databases, but hope that these notes will continue to be of benefit to others.

About the author: is a dedicated software developer and webmaster. For his day job he develops websites and desktop applications as well as providing IT services. He moonlights as a technical author and consultant.