数据库alert日志报如下错误
Tue Feb 15 12:24:11 2011
Errors in file /oracle/admin/xxx/udump/gis_ora_14220.trc:
ORA-00600: internal error code, arguments: [525], [0xC00000007478BD68], [4], [row cache objects], [3], [0xC000000281265160], [child cursor hash table], []
trace file xxx_ora_14220.trc:
-----------------------------------------------------------------------------------------
*** SESSION ID:(472.13895) 2011-02-15 12:24:11.615
*** 2011-02-15 12:24:11.615
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [525], [0xC00000007478BD68], [4], [row cache objects], [3], [0xC000000281265160], [child cursor hash table], []
Current SQL statement for this session:
select /*+ first_rows(10)*/ t1.task_id,t1.order_id,t1.tache,t1.order_type from xxx_task t1 where t1.order_state = :1 and t1.tache = :2 and rownum <= :3
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedmp()+184 ? ksedst() 4000000001617953 ?
000000002 ?
4000000000806920 ?
40000000011951C7 ?
ksfdmp()+32 ? ksedmp() 800003FFBFFF8728 ?
30005D3A8 ?
4000000000396BE8 ?
400000000131D0B7 ?
kgeriv()+152 ? ksfdmp() 4000000000396BE8 ?
----------------------------------------------------------------------------------------------------------
在metalink查询,确认此错误可以忽略,由于没有对应的bug,而9i已经不提供支持了,也只有标记一下,忽略了
| ORA-600 [525] [ID 138888.1] | |||||
|
| |||||
| 修改时间 07-SEP-2010 类型 REFERENCE 状态 PUBLISHED | |||||
Note: For additional ORA-600 related information please read Note:146580.1 PURPOSE: This article discusses the internal error "ORA-600 [525]", what it means and possible actions. The information here is only applicable to the versions listed and is provided only for guidance. ERROR: ORA-600 [525] [a] [b] [c] [d] [e] [f] VERSIONS: versions 7.3 to 10.1 DESCRIPTION: This error is raised when a latch request violates the ordering rules. Each parent latch has a hard-coded level# (level number) inherited by all its child latches. Each child latch is assigned a child# (child number). The latch level#'s and child#'s are used to ensure all processes which acquire multiple latches, acquire them in the same strict order. This will prevent deadlocks between processes. This internal error is raised when a second latch request violates the ordering rules. ARGUMENTS: Arg [a] Address of Child Latch being requested Arg [b] Level of Latch (level#) Arg [c] Name of requested Latch Arg [d] Child number of requested Latch (child#) Arg [e] Address of Latch currently owned Arg [f] Name of Latch currently owned FUNCTIONALITY: Kernel Service layer Latching & Wait-post Implementation IMPACT: PROCESS FAILURE NON CORRUPTIVE - No underlying data corruption. SUGGESTIONS: If the Known Issues section below does not help in terms of identifying a solution, please submit the trace files and alert.log to Oracle Support Services for further analysis. Known Issues: function getdoc(docstr) { pos=docstr.indexOf(':'); docid=docstr.substring(pos+1,docstr.length); tgt="_self"; if ( location.href.slice(7,12) == "webiv" || location.href.slice(7,11) == "rmsu" ) { loc="Get?WwwID=note:" + docid; window.open(loc,tgt) return; } if ( location.href.slice(7,12) == "metal" || location.href.slice(7,12) == "suppo" ) { loc="showdoc?db=NOT&id=" + docid; window.open(loc,tgt) return; } else { loc="http://metalink.oracle.com/metalink/plsql/showdoc"+ "?db=NOT&id="+docid; window.open(loc,tgt) return; } } Known Bugs
NB Bug Fixed Description 9398918 11.2.0.2 OERI [525] when rekeying master key on HSM device 5894422 10.2.0.4, 11.1.0.7, 11.2.0.1 OERI[525] / OERI[kglsim_rebalru2] 5115857 RMAN backup ends with OERI[525] 4202347 10.1.0.5, 10.2.0.1 ASM may crash with OERI:525 2588590 9.2.0.4, 10.1.0.2 OERI[525] possible while growing the cursor hash table 2742518 9.2.0.4, 10.1.0.2 Accessing X$GLOBALCONTEXT may fail with OERI:525 / hangs the DB 3752329 9.2.0.7 OERI[525] on [kjct flow control latch] in RAC
来自 “ ITPUB博客 ” ,链接:https://blog.itpub.net/11088128/viewspace-687264/ ,如需转载,请注明出处,否则将追究法律责任。