ORA-00314, redolog corruption, or missing Handling Methods

ORA-00314, redolog corruption, or loss of processing method alertsid. log error message:

Fri Sep 27 15:18:39 2013Started redo scanFri Sep 27 15:18:39 2013Errors in file /oracle/admin/lixora/udump/lixora_ora_23439.trc:ORA-00314: log 2 of thread 1, expected sequence# 335 doesn't match 331ORA-00312: online log 2 thread 1: '/oracle/oradata/lixora/redo02.log'Fri Sep 27 15:18:39 2013Aborting crash recovery due to error 314

 

View the current log group information:

SQL> select * From v$log;    GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS---------- ---------- ---------- ---------- ---------- --- ----------------FIRST_CHANGE# FIRST_TIM------------- ---------         1          1        334   52428800          1 NO  ACTIVE      3613897 27-SEP-13         4          1        333  104857600          1 NO  INACTIVE      3613895 27-SEP-13         3          1        336   52428800          1 NO  CURRENT      3613948 27-SEP-13         2          1        335   52428800          1 NO  ACTIVE      3613899 27-SEP-13

 

If the online redo log of the specified region is inactive when you query v $ log, it indicates that the Group log is not a pre-existing log and has been completed successfully (the STATUS is INACTIVE, ARCHIVE is YES ). processing Method (used for batch operation and non-linear operation): Use the clear command to clear the redo log group where the file is located. SQL> alter database clear logfile group 3; if the log group does not have dynamic connections (STATUS is INACTIVE, ARCHIVE is NO) then, run the following command SQL> alter database clear unarchived logfile group 3; then open a data volume and copy it.