ORA-600(kjxgrdecidemem1)錯誤
對客戶資料庫進行檢查的時候,發現告警日誌中存在這個錯誤資訊。
詳細錯誤資訊如下:
Wed Feb 23 23:08:08 2011
IPC Send timeout detected.Sender: ospid 164136
Receiver: inst 1 binc 1003211226 ospid 111572
Wed Feb 23 23:08:09 2011
IPC Send timeout to 0.0 inc 4 for msg type 12 from opid 38
Wed Feb 23 23:08:09 2011
Communications reconfiguration: instance_number 1
Waiting for clusterware split-brain resolution
Wed Feb 23 23:08:09 2011
Trace dumping is performing id=[cdmp_20110223230809]
Wed Feb 23 23:08:28 2011
IPC Send timeout detected. Receiver ospid 188622
Wed Feb 23 23:08:28 2011
Errors in file /oracle/app/oracle/admin/fdjdb/bdump/fdjdb2_pz98_188622.trc:
Wed Feb 23 23:08:59 2011
IPC Send timeout detected.Sender: ospid 278920
Receiver: inst 1 binc 1003211235 ospid 270504
Wed Feb 23 23:08:59 2011
IPC Send timeout detected.Sender: ospid 283050
Receiver: inst 1 binc 1003211248 ospid 258542
Wed Feb 23 23:09:00 2011
IPC Send timeout to 0.1 inc 4 for msg type 32 from opid 43
Wed Feb 23 23:09:31 2011
IPC Send timeout to 0.4 inc 4 for msg type 32 from opid 39
Wed Feb 23 23:12:26 2011
Trace dumping is performing id=[cdmp_20110223231226]
Wed Feb 23 23:12:38 2011
Errors in file /oracle/app/oracle/admin/fdjdb/bdump/fdjdb2_lmon_209424.trc:
ORA-00600: internal error code, arguments: [kjxgrdecidemem1], [], [], [], [],
[], [], []
Wed Feb 23 23:12:39 2011
Errors in file /oracle/app/oracle/admin/fdjdb/bdump/fdjdb2_lmon_209424.trc:
ORA-00600: internal error code, arguments: [kjxgrdecidemem1], [], [], [], [],
[], [], []
Wed Feb 23 23:12:39 2011
LMON: terminating instance due to error 481
Wed Feb 23 23:12:39 2011
Trace dumping is performing id=[cdmp_20110223231239]
Wed Feb 23 23:12:40 2011
Shutting down instance (abort)
License high water mark = 12
Wed Feb 23 23:12:44 2011
Instance terminated by LMON, pid = 209424
Wed Feb 23 23:12:50 2011
Instance terminated by USER, pid = 344090
之所以在ORA-600錯誤的前後包括了很多的內容,是因為導致這個錯誤出現的原因就在這些內容中。
在CLUSTER執行RECONFIGURATION的時候,如果例項執行SHUTDOWN,就會導致這個錯誤的出現。對應的錯誤資訊為Bug 4153410。這個錯誤在10.2.0.5中被fixed,而使用者的版本是10.2.0.4。
這個錯誤對系統並沒有什麼危害,而Oracle的文件對這個問題的建議就是,在執行CLUSTER RECONFIGURATION的時候不要關閉資料庫。
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/4227/viewspace-701337/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- ORA-600(kffmXpGet)錯誤
- ORA-600(kcbgcur_1)錯誤GC
- ORA-600 [ttcgcshnd-1 ]錯誤GC
- ORA-600(kclgclk_7)錯誤GC
- ORA-600(kcbnew_3)錯誤
- ORA-600(qersqCloseRem-2)錯誤REM
- ORA-600(qctopn1)錯誤
- ORA-600(kcblasm_1)錯誤ASM
- ORA-600(qkaffsindex5)錯誤Index
- ORA-600(kghuclientasp_03)錯誤client
- ORA-600(ttcgcshnd-2)錯誤GC
- ORA-600(kolaslGetLength-1)錯誤
- ORA-600(kghfremptyds)和ORA-600(kghasp1)錯誤REM
- ORA-600(kssadd: null parent)錯誤Null
- ORA-600(504)(row cache objects)錯誤Object
- ORA-600(ktrgcm_3)錯誤GC
- ORA-600(krvxdds: duplicated session not)錯誤Session
- ORA-600(kfioUnidentify01)錯誤IDE
- ORA-600(qsmqSetupTableMetadata-2)錯誤MQ
- ORA-600(kcratr_scan_lastbwr)錯誤AST
- ORA-600(ksnpost:ksnigb)錯誤
- ORA-600(evapth : unexpected evaluation)錯誤APT
- ORA-600(qkacon:FJswrwo)錯誤JS
- ORA-600(KSFD_DECAIOPC)和ORA-600(kfioReapIO00)錯誤AIAPI
- ORA-600(kocgor077)錯誤Go
- ora-600內部錯誤的型別型別
- ORA-600(kkoipt:invalid join method)錯誤
- ORA-600[6122]錯誤處理
- ORA-600(krboReadBitmap_badbitmap)錯誤
- ORA-600(kcbchg1_12)和ORA-600(kdifind:kcbget_24)錯誤
- ORA-600(ktfbbsearch-8)和ORA-600(kewrose_1)錯誤ROS
- ORA-600(kjbrchkpkeywait:timeout)和ORA-600(kclcls_8)錯誤AI
- ORA-600(kauxs_do_jou:3)錯誤UX
- oracle 10.2.0.5 平臺上ORA-600錯誤Oracle
- ORA-600(kcbz_check_objd_typ_3)錯誤OBJ
- ORA-600(kgscLogOff-notempty)錯誤Go
- ORA-600(kssadd_stage: null parent)錯誤Null
- ORA-600[4000]/[4097]錯誤的處理