12月中午,北京局的一同事找到我,说他的一个新装的数据库错误:
ORA-600 [17114]
通过查看分析metalink相关文档:
|
||
|
||
|
|
|
Note: For additional ORA-600 related information please read
Note:146580.1
PURPOSE:
This article discusses the internal error “ORA-600 [17114]”, what
it means and possible actions. The information here is only applicable
to the versions listed and is provided only for guidance.
ERROR:
]/g,’>’); msgfld = document.getElementById(“FullMsg”); msgfld.innerHTML += ”
Supplied Error Message: ORA-600 [17114]”+ arglst.toLowerCase(); } return; }
Format: ORA-600 [17114] [a]
VERSIONS:
versions 7.0 and above
DESCRIPTION:
Oracle has detected that the magic number in a memory chunk header has been
overwritten.
This is a heap (in memory) corruption and there is no underlying data
corruption.
The error may occur in the one of the process specific heaps
(the Call heap, PGA heap, or session heap) or in the shared heap (SGA).
ARGUMENTS:
Arg [a] Pointer to chunk header
FUNCTIONALITY:
HEAP MANAGEMENT
IMPACT:
PROCESS FAILURE
MEMORY CORRUPTION, POSSIBLE INSTANCE FAILURE
NON DATA CORRUPTIVE – No underlying data corruption.
SUGGESTIONS:
If you think you are not hitting any of the known issues shown below,
then you need to set event 10235 in your init.ora file :-
event=”10235 trace name context forever, level 1″
While the event is set, the next time you get the error a trace
file will be generated in your USER_DUMP_DEST directory.
Contact Oracle Support Services and supply the trace file.
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
0) { // MUST have this tag if (affects==null || affects.indexOf(t)<0) { display=0; // but we do not have it } } else { if (Tags[t]0) { dig=iver.substr(0,1); if (dig==’.’) { return(res+iver); } if (dig==’0′) { dig=iver.substr(1,1); } else { dig=iver.substr(0,2); } res=res+sep+dig; sep=’.’; iver=iver.substr(2); } return(res); } function IamOn(ver){ Ver=ver; ShowRows(); var titl = document.getElementById(“BugListInfo”); if (titl!=null) { if (ver==null) { titl.innerHTML=”The list below shows bugs affecting any version”; } else { titl.innerHTML=”The list below is restricted to show only bugs “+ “believed to affect version “+NiceVer(ver)+”.
“+ “Other bugs may affect this version “+ ” but have not been confirmed as being relevant yet.”; } } } // ===== ACT ON URL ===== window.onload = SetVer; // ======================
窗体顶端
You can restrict the list below to issues likely to affect one of the following versions by clicking the relevant button:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
·
‘*’
against a bug indicates that an alert exists for that issue.
·
‘+’
indicates a particularly notable bug.
·
‘P’
indicates a port specific bug.
·
“OERI:
nnnnn
” is used as shorthand for
ORA-600 [
nnnnn
]
.
Bug# 898074
PRIVATE MEM CORR ON PARTITION TABLE & NON-PARTITION-KEY PREDICATE
Fixed: 8.0.6.1, 8.1.6.0
Bug# 573746
DBMS_SQL DEFINE_ARRAY / ARRAY FETCH TO LARGE ARRAY MAY CAUSE ORA-600[17114]
Fixed: 8.0.4.4, 8.0.5.0, 8.1.5.0
|
这个oracle的一个bug。
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/12129601/viewspace-713660/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/12129601/viewspace-713660/