ORA-00346 Log member marked as STALE and closed
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: 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.
Cause: The control file change sequence number in the log file is greater than the number in the control file. This implies that the wrong control file is being used. Note that repeatedly causing this error can make it stop happening without correcting the real problem. Every attempt to open the database will advance the…
Cause: The internal information in an online log file does not match the control file. Action: Restore correct file or reset logs.
Cause: The log is smaller than the space allocated in it. May be the result of a shutdown abort while it was being written by the archiver. Action: Get a complete version of this log and use it for recovery. There should either be an online version of it or a copy that was successfully…