ORA-00318: log string of thread string, expected file size string doesn’t match string
Cause: On header read the file size indicated in the control file did not match the file size contained in the log file.
Action: Restore correct file or reset logs.
ORA-00317: file type string in header is not log file
Cause: This is not an archived log file.
Action: Find the correct file and try again.
ORA-00316: log string of thread string, type string in header is not log file
Cause: The online log is corrupted or is an old version.
Action: Find and install correct version of log or reset logs.
ORA-00315: log string of thread string, wrong thread # string in header
Cause: The online log is corrupted or is an old version.
Action: Find and install correct version of log or reset logs.
ORA-00314: log string of thread string, expected sequence# string doesn’t match string
Cause: The online log is corrupted or is an old version.
Action: Find and install correct version of log or reset logs.
ORA-00313: open failed for members of log group string of thread string
Cause: The online log cannot be opened. May not be able to find file.
Action: See accompanying errors and make log available.
ORA-00312: online log string thread string: ‘string’
Cause: This message reports the filename for details of another message.
Action: Other messages will accompany this message. See the associated messages for the appropriate action to take.
ORA-00311: cannot read header from archived log
Cause: An I/O error occurred when attempting to read the log file header from the specified archived redo log file.
Action: Other messages will accompany this message. See the associated messages for the appropriate action to take.
ORA-00310: archived log contains sequence string; sequence string required
Cause: The archived log is out of sequence, probably because it is corrupted or the wrong redo log filename was specified
Action: Specify the correct redo log file; then retry the operation.
ORA-00309: log belongs to wrong database
Cause: The system cannot access the archived redo log because it belongs to another database.
Action: Specify the correct redo log file, then retry the operation.