ORA-00346: REDO LOG FILE HAS STATUS 'STALE' (Doc ID 1014824.6)

Last updated on NOVEMBER 22, 2023

Applies to:

Symptoms

Problem Description: 
==================== 
 
Querying V$LOGFILE, you notice that a redo log file has a status of "STALE".  
For example: 
 
    SQLDBA> SELECT * FROM V$LOGFILE; 
 
    GROUP#     STATUS  MEMBER 
    ---------- ------- ------------------------------ 
             1 STALE   /oracle/7.3.4/dbs/log1P734.dbf 
 
             2         /oracle/7.3.4/dbs/log2P734.dbf 
 
             3         /oracle/7.3.4/dbs/log3P734.dbf 
 
You may also see an ORA-00346 in your alert.log file or in a LGWR trace file: 
 
    ORA-00346: log member marked as STALE 
        Cause: A log file member no longer is complete. 
       Action: Correct the underlying problem by referring to the other error 
               messages found with this one. 
 
In addition, you might see error messages like: 
 
    ORA-00345: redo log write error block %s count %s 
        Cause: An IO error has occurred while writing the log 
       Action: Correct the cause of the error, and then restart the system. 
               If the log is lost, apply media/incomplete recovery. 
  
    ORA-00312: online log %s thread %s: '%s' 
        Cause: Reporting file name for details of another error 
       Action: See associated error messages 
 
and an operating system level Oracle message such as ORA-07376: 
 
    ORA-07376: sfwfb: write error, unable to write database block. 
        Cause: Additional information returns block number. 
       Action: Check errno. Check block number. 
 
Log files may have a status of stale regardless of redo log mirroring or 
archival mode. 

Cause