Site icon IT Tutorial

ORA-00314: log string of thread string, expected sequence# string doesn’t match string

Mehmet Salih Deveci

I got ” ORA-00314: log of thread, expected sequence# nn doesn’t match ”  error in Oracle database.

 

ORA-00314: log of thread, expected sequence# nn doesn’t match

 

Details of error are as follows.

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.



 


 


log string of thread string, expected sequence# string doesn’t match string


This ORA-00314 error is related to the online log is corrupted or is an old version.


 


Following errors are received when attempting to startup standby or while logs are being applied


ORA-00314: log 404 of thread 4, expected sequence# 33808 doesn't match 33543
ORA-00312: online log 404 thread 4: '+<path>/onlinelog/group_404.468.703522549'
ORA-00314: log 404 of thread 4, expected sequence# 33808 doesn't match 33543
ORA-00312: online log 404 thread 4: '+<path>/onlinelog/group_404.450.703522549'








Standby redo is being used.

while archives are being transferred, network outage, instance crash occurred.










Standby redo has corrupt entry.


Instance crash while redo entry being transfer/received


The error message with ora-314 tells you the standby redo with corruption


ie)

ORA-00314: log 404 of thread 4, expected sequence# 33808 doesn’t match 33543




==> redo log group (# 404) is the one with corruption.


When problem (instance crash,network problem) happened, it was receiving sequence 33808 and was corrupted in the middle. so the header has info on sequence 33808 but current archive sequence # being transferred is 33543.You may see the another standby redo is receiving the sequence# 33543 in v$standby_log with two of them are active status





v$standby_log
------------------------

GROUP# DBID THREAD# SEQUENCE#
---------- ---------------------------------------- ---------- ----------
BYTES USED ARC STATUS FIRST_CHANGE# FIRST_TIME
---------- ---------- --- ---------- ------------- -------------------
LAST_CHANGE# LAST_TIME
------------ -------------------
401 1863397730 4 34381
104857600 93738496 YES ACTIVE 5.9903E+12 Jan 28 2010 05:22PM
5.9903E+12 Jan 28 2010 06:52PM



404 1863397730 4 33808
104857600 0 YES ACTIVE 5.9902E+12 Jan 24 2010 02:04AM
5.9903E+12 Jan 28 2010 06:52PM

------------------------------------------------------












Clear standby redo with ora-314 error.


Stop recovery on standby side.


SQL> Alter database recover managed standby database cancel;


 


clear standby redo group 404.


 


SQL>  alter database clear logfile group 404;


You may have to use the ‘unarchived’-Keyword to be able to clear the Standby RedoLog Group in most Cases, eg.


 


SQL> alter database clear unarchived logfile group 404;




 


Do you want to learn Oracle Database for Beginners, then read the following articles.



Oracle Tutorial | Oracle Database Tutorials for Beginners  ( Junior Oracle DBA )


 




	


	






		

			
				Exit mobile version