Cause: The redo block indicated by the accompanying error, is not vaild. It has a checksum that does not match the block contents. 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…

Cause: An attempt to switch the current log of a single thread is not allowed because the compatiblity requirements force a new log format version number. When changing log formats, all threads must switch to the new format at the same time. Action: Open the database to cause the coordinated log switch. If that is…

Cause: The file header for the redo log contains a checksum that does not match the value calculated from the file header as read from disk. This means the file header is corrupted Action: Find the correct file and try again.

Cause: An attempt to switch to a new online log for the redo thread failed because no reusable log could be found. This log is being cleared and will be useable when the clearing completes. The command that began the clearing may have terminated without completing the clearing. Action: If the clear command is still…

Cause: A request to drop a logfile member was denied because it would remove data required to form a complete logfile. Action: If desired, delete the entire log (after archiving if required), by using DROP LOGFILE;

Cause: An add logfile member or drop logfile request specified a logfile group number that does not exist. Action: Check the configuration of the log files and reissue the command.

Cause: The log given to recovery is a backup of the online version from the time it was the current log. The archived version of the log would not be marked as end of thread. This error can also be caused by failing to list the current log of an enabled thread in a CREATE…