Cause: A change record in the redo log contains lengths that do not add up to a consistent value. The log is corrupted in some way. Action: Do recovery with a good version of the log or do time based recovery up to the indicated time.
Cause: Attempting to enable a thread with all logs needing to be archived, and media recovery has been enabled. There is no log that can be made the new current log for the thread. Action: Archive a log for the thread or disable media recovery.
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.