Cause: The operating system was unable to determine the blocksize for the given filename. Action: Consult the accompanying error message, and correct the device or specify another filename.

Cause: The block header on the redo block indicated by the accompanying error, is not reasonable. Action: Do recovery with a good version of the log or do time based recovery up to the indicated time. If this happens when archiving, archiving of the problem log can be skipped by clearing the log with the…

Cause: The time specified in a recover-until statement must be after January 1st 1988. Action: Specify a time after January 1st 1988.

Cause: A log file member was no longer complete. Action: Correct the underlying problem by referring to the other error messages found with this one.

Cause: The command cannot be done because the log has not been archived, and media recovery has been enabled. Action: Archive the log or disable media recovery. If the command supports an UNARCHIVED option then it can be used. However this may result in making backups unuseable, and forcing the drop of some offline files.

Cause: A failure occurred during a critical portion of the log code during single process operation. This error does not occur during normal multi-process operation. Action: Shutdown abort and warmstart the database.

Cause: Reporting filename for details of another error Action: See associated error messages

Cause: On header read the blocksize indicated in the control file did not match the blocksize contained in the log file. Action: Restore correct file or reset logs.

Cause: The archived log is not the correct log. It is a copy of a log file that has never been used for redo generation, or was an online log being prepared to be the current log. Action: Restore the correct log file.

Cause: Recovery was given a log that does not belong to current incarnation or one of the parent incarnation. There should be another log that contains the correct redo. Action: Supply the correct log file.