ORA-00314: log 20 of thread 1, expected sequence# 108055 doesn't match 108053
转载请注明出处：http://blog.csdn.net/xiaofan23z
Ora-00314
Symptom：
*** 2012-03-30 16:55:32.921
*** SERVICE NAME:() 2012-03-30 16:55:32.920
*** SESSION ID:(139.1) 2012-03-3016:55:32.920
ORA-00314: log 20 of thread 1, expected sequence# 108055 doesn't match 108053
ORA-00312: online log 20 thread 1:'+STANDBY_ARCH/sfc12stb/onlinelog/group_20.1261.735834135'
ORA-00314: log 20 of thread 1, expectedsequence# 108055 doesn't match108053
ORA-00312: online log 20 thread 1: '+STANDBY_DATA/sfc12stb/onlinelog/group_20.517.735834133'
ORA-00314: log 20 of thread 1, expectedsequence# 108055 doesn't match 108053
ORA-00312: online log 20 thread 1:'+STANDBY_ARCH/sfc12stb/onlinelog/group_20.1261.735834135'
ORA-00314: log 20 of thread 1, expectedsequence# 108055 doesn't match 108053
ORA-00312: online log 20 thread 1:'+STANDBY_DATA/sfc12stb/onlinelog/group_20.517.735834133'
Solution：
sys@sfc12db> Alter database recover managed standby database cancel;
Database altered.
sys@sfc12db> select * from v$standby_log;
GROUP# DBID THREAD# SEQUENCE# BYTES USED ARC STATUS FIRST_CHANGE# FIRST_TIME LAST_CHANGE#
---------------------------------------------- ------- ---------- -------------------- --- ---------- --------------- ------------ ------------
LAST_TIME
------------
161192333070 3 108147 104857600 8314880 YES ACTIVE 219436391739 30-MAR-12 2.1944E+11
30-MAR-12
171192333070 2 107586 104857600 31790080 YES ACTIVE 219435057563 30-MAR-12 2.1944E+11
30-MAR-12
18UNASSIGNED 2 0 104857600 1024 NO UNASSIGNED 0 0
19UNASSIGNED 3 0 104857600 1024 NO UNASSIGNED 0 0
20 1192333070 1 108055 104857600 0 YESACTIVE 219427350191 30-MAR-12 2.1944E+11
30-MAR-12
发现group 20 中的这个log 一直在active，实际上这个log已经被应用过了。
21UNASSIGNED 1 0 104857600 1024 NO UNASSIGNED 0 0
221192333070 1 108065 104857600 23578624 YES ACTIVE 219436468496 30-MAR-12 2.1944E+11
30-MAR-12
23UNASSIGNED 2 0 104857600 1024 NO UNASSIGNED 0 0
24UNASSIGNED 3 0 104857600 1024 NO UNASSIGNED 0 0
GROUP# DBID THREAD# SEQUENCE# BYTES USED ARC STATUS FIRST_CHANGE# FIRST_TIME LAST_CHANGE#
---------------------------------------------- ------- ---------- -------------------- --- ---------- --------------- ------------ ------------
LAST_TIME
------------
25UNASSIGNED 3 0 104857600 1024 NO UNASSIGNED 0 0
26UNASSIGNED 2 0 104857600 1024 NO UNASSIGNED 0 0
27UNASSIGNED 1 0 104857600 1024 NO UNASSIGNED 0 0
28UNASSIGNED 0 0 104857600 1024 YES UNASSIGNED 0 0
29UNASSIGNED 0 0 104857600 1024 YES UNASSIGNED 0 0
30UNASSIGNED 0 0 104857600 1024 YES UNASSIGNED 0 0
15 rows selected.
sys@sfc12db> alter database clear logfile group 20; ##将这个redo group清空
Database altered.
sys@sfc12db> select * from v$standby_log; ##查询确认
GROUP# DBID THREAD# SEQUENCE# BYTES USED ARC STATUS FIRST_CHANGE# FIRST_TIME LAST_CHANGE#
------ ----------------------------------------------- ---------- ---------- ---------- --- ---------- --------------------------- ------------
LAST_TIME
------------
161192333070 3 108147 104857600 8444928 YES ACTIVE 219436391739 30-MAR-12 2.1944E+11
30-MAR-12
171192333070 2 107586 104857600 32610304 YES ACTIVE 219435057563 30-MAR-12 2.1944E+11
30-MAR-12
18UNASSIGNED 2 0 104857600 1024 NO UNASSIGNED 0 0
19UNASSIGNED 3 0 104857600 1024 NO UNASSIGNED 0 0
20UNASSIGNED 1 0 104857600 104857600 YES UNASSIGNED 219427350191 30-MAR-12 2.1944E+11
30-MAR-12
##已经被清除
21UNASSIGNED 1 0 104857600 1024 NO UNASSIGNED 0 0
221192333070 1 108065 104857600 28276736 YES ACTIVE 21943646849630-MAR-12 2.1944E+11
30-MAR-12
23UNASSIGNED 2 0 104857600 1024 NO UNASSIGNED 0 0
24UNASSIGNED 3 0 104857600 1024 NO UNASSIGNED 0 0
GROUP# DBID THREAD# SEQUENCE# BYTES USED ARC STATUS FIRST_CHANGE# FIRST_TIME LAST_CHANGE#
---------------------------------------------- ------- ---------- -------------------- --- ---------- --------------- ------------ ------------
LAST_TIME
------------
25UNASSIGNED 3 0 104857600 1024 NO UNASSIGNED 0 0
26UNASSIGNED 2 0 104857600 1024 NO UNASSIGNED 0 0
27UNASSIGNED 1 0 104857600 1024 NO UNASSIGNED 0 0
28UNASSIGNED 0 0 104857600 1024 YES UNASSIGNED 0 0
29UNASSIGNED 0 0 104857600 1024 YES UNASSIGNED 0 0
30UNASSIGNED 0 0 104857600 1024 YES UNASSIGNED 0 0
15 rows selected.
##重新启用redo log real time apply
sys@sfc12db> alter database recover managed standby databasedisconnect;
Database altered.
sys@sfc12db> alter database recover managed standby databasecancel;
Database altered.
sys@sfc12db> alter database recover managed standby databaseusing current logfile disconnect;
Database altered.
sys@sfc12db> exit
转载请注明出处：http://blog.csdn.net/xiaofan23z
metalink solution
| ORA-00314: LOG 404 OF THREAD 4, EXPECTED SEQUENCE# 33808 DOESN'T MATCH 33543 [ID 1077564.1] |
||
|
|
||
|
|
Modified 15-APR-2011 Type PROBLEM Status PUBLISHED |
|
Inthis Document
Symptoms
Changes
Cause
Solution
Applies to:
Oracle Server - Enterprise Edition - Version: 10.1.0.5 to11.2.0.2 - Release: 10.1 to 11.2
Information in this document applies to any platform.
Symptoms
Following errors are received when attempting to startup standby or while logsare being applied
ORA-00314: log 404 of thread 4, expected sequence# 33808doesn't match 33543
ORA-00312: online log 404 thread 4:'+INDEX01/test/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:'+DATA01/test/onlinelog/group_404.450.703522549'
Changes
Standby redo is being used.
while archives are being transferred, network outage, instance crash occurred.
Cause
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 receivingsequence 33808 and was corrupted in the middle. so the header has info onsequence 33808 but current archive sequence # being transferred is 33543.
You may see the another standby redo is receiving the sequence# 33543 inv$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
------------------------------------------------------
Solution
Clear standby redo with ora-314 error.
Stop recovery on standby side.
SQL> Alter database recover managed standbydatabase 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 StandbyRedoLog Group in most Cases, eg.
SQL>alter database clear unarchived logfile group 404;
| Related Products · Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition Keywords
Errors
转载请注明出处：http://blog.csdn.net/xiaofan23z |