| ERROR | expected archived log not found, lost of archived log compromises recoverability |
| CAUSE | The archived log was not found. The repository thinks it does exist. If the archived log has in fact been lost and there is no backup, then the database is no longer recoverable across the point in time covered by the archived log. This may occur because the archived log was removed by an outside utility without updating the repository. |
| ACTION | If the archived log has been removed with an outside utility and the archived log has already been backed up, then you can synchronize the repository by running CROSSCHECK ARCHIVELOG ALL. If the archived log has not been previously backed up, then you should take a full backup of the database and archived logs to preserve recoverability. Previous backups are not fully recoverable. |