600 【12333】不影響db執行的bug嗎

資料庫中日誌基本不切換，db基本沒有負載，檢視警告日誌中發現在出現了ora-00600後，redo的切換就不正常了，這裡也提醒下資料庫沒有問題不代表真的沒問題，對於系統有些異常情況需要及時去檢視後臺日誌來診斷具體的資訊。系統主機也沒有什麼負載。

Thu May 3 12:29:28 2012

ORA-00060: Deadlock detected. More info in file /db/oracle10g/admin/benguo/udump/benguo_ora_21458.trc.

Thu May 3 12:41:22 2012

ORA-00060: Deadlock detected. More info in file /db/oracle10g/admin/benguo/udump/benguo_ora_21430.trc.

Thu May 3 12:56:11 2012

ORA-00060: Deadlock detected. More info in file /db/oracle10g/admin/benguo/udump/benguo_ora_21568.trc.

Thu May 3 13:29:26 2012

ORA-00060: Deadlock detected. More info in file /db/oracle10g/admin/benguo/udump/benguo_ora_21469.trc.

Thu May 3 13:36:04 2012

Errors in file /db/oracle10g/admin/benguo/udump/benguo_ora_21650.trc:

ORA-00600: internal error code, arguments: [12333], [19], [3], [15], [], [], [], []

Thu May 3 14:01:20 2012

Thread 1 advanced to log sequence 4402

Current log# 4 seq# 4402 mem# 0: /db/oracle10g/oradata/benguo/redo04.log

Thu May 3 15:28:13 2012

Errors in file /db/oracle10g/admin/benguo/udump/benguo_ora_21646.trc:

ORA-00600: internal error code, arguments: [12333], [19], [3], [15], [], [], [], []

Thu May 3 18:01:25 2012

Thread 1 advanced to log sequence 4403

Current log# 5 seq# 4403 mem# 0: /db/oracle10g/oradata/benguo/redo05.log

Trace檔案

*** SERVICE NAME:(SYS$USERS) 2012-05-04 14:06:53.162

*** SESSION ID:(412.37869) 2012-05-04 14:06:53.162

*** 2012-05-04 14:06:53.162

ksedmp: internal or fatal error

ORA-00600: internal error code, arguments: [12333], [19], [3], [94], [], [], [], []

Current SQL statement for this session:

SELECT COUNT(f_article_id) AS f_article_id FROM textauto_folderarticle WHERE f_folder_id = :1

----- Call Stack Trace -----

calling call entry argument values in hex

location type point (? means dubious value)

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

ksedst()+31 call ksedst1() 000000000 ? 000000001 ?

000000000 ? 000000000 ?

000000000 ? 000000001 ?

ksedmp()+610 call ksedst() 000000000 ? 000000001 ?

000000000 ? 000000000 ?

000000000 ? 000000001 ?

ksfdmp()+21 call ksedmp() 000000003 ? 000000001 ?

000000000 ? 000000000 ?

000000000 ? 000000001 ?

kgeriv()+176 call ksfdmp() 000000003 ? 000000001 ?

000000000 ? 000000000 ?

000000000 ? 000000001 ?

kgesiv()+119 call kgeriv() 005EBDCA0 ? 2AEA455E2160 ?

000000001 ?

根據該trace檔案是這個sql語句的繫結變數後導致的錯誤，由於網路上沒有過多的解釋，採取的重啟java程式，後續這個錯誤就沒有發生了，日誌也切換正常了！

http://www.itpub.net/thread-1422637-1-1.html

http://www.itpub.net/thread-249828-2-1.html

的ITPUB中帖子中也出現了同樣的問題，關於其中的緣由網友給出的解答貌似是個bug導致，不過該內部錯誤是否導致了系統日誌切換問題應該不太可能，因為在同樣的正常的日誌切換的資料庫中依然發現此類錯誤，更可能相信是一個不影響db的小bug，而且出現問題的資料庫正是10.2.0.1.0版本，在oracle 11g下已經解決

db: 10.2.0.0---&gt10.2.0.3.0
os: all

Metalink DocID: Note:464321.1

Stack trace is similar to:

ksedst ksedmp ksfdmp kgeriv kgesiv ksesic3
opitsk opiino opiodr opidrv sou2o opimai_real
main $START$


Cause:
This is Bug 5926074
Abstract: ORA-600 [12333] UPDATE CLOB

If you update on two clob columns and you get ora-600[12333], then you hit this
bug.

solution:

a. fixed in Oracle server version 11.0

b. get the patch: 5926074 for you specify os

[@more@]