首页 » ORACLE 9i-23c » Troubleshooting ora-600 [17114] Trace file show current SQL selecting v$session
Troubleshooting ora-600 [17114] Trace file show current SQL selecting v$session
二个月前一套CRM 的10.2.0.5 rac on hpux 的alert 中发现了ora-600 17114 , 从trace file 中发现是查询v$session, 随后在MOS中找到了bug 导致， call stack 一致，简单记录一下。（注：虽然本机没有安装OMS,但依旧可以确认是该问题）
/opt/oracle/app/admin/anbob/bdump/anbob2_lmd0_22503.trc. Wed Dec 31 18:04:30 EAT 2014 Errors in file /opt/oracle/app/admin/anbob/bdump/anbob2_pz99_22761.trc: ORA-00600: internal error code, arguments: [17114], [0x9FFFFFFFFD3332F0], [], [], [], [], [], [] Wed Dec 31 18:05:33 EAT 2014 Thread 2 advanced to log sequence 52557 (LGWR switch) Current log# 7 seq# 52557 mem# 0: /dev/vg_crm02/rvgcrm02_redo03 Wed Dec 31 18:07:08 EAT 2014 Immediate Kill Session#: 2628, Serial#: 12057 Immediate Kill Session: sess: c0000019fd8fa348 OS pid: 9106 Wed Dec 31 18:07:44 EAT 2014 Trace dumping is performing id=[cdmp_20141231180744] Wed Dec 31 18:07:45 EAT 2014 Errors in file /opt/oracle/app/admin/anbob/bdump/anbob2_pz99_22761.trc: ORA-00600: internal error code, arguments: [17114], [0x9FFFFFFFFD3332F0], [], [], [], [], [], [] ORA-00600: internal error code, arguments: [17114], [0x9FFFFFFFFD3332F0], [], [], [], [], [], [] Wed Dec 31 18:07:48 EAT 2014 Errors in file /opt/oracle/app/admin/anbob/bdump/anbob2_pz99_22761.trc: ORA-00600: internal error code, arguments: [17114], [0x9FFFFFFFFD3332F0], [], [], [], [], [], [] ORA-00600: internal error code, arguments: [17114], [0x9FFFFFFFFD3332F0], [], [], [], [], [], [] Wed Dec 31 18:10:49 EAT 2014
# trace file
Current SQL statement for this session:
SELECT round(bitand(s.ownerid, 65535)) parent_session_sid, round(bitand(s.ownerid,16711680)/65536) parent_session_instid, s.INST_ID, s.SA
DDR, s.SID, s.SERIAL#, s.AUDSID, s.PADDR, s.USER#, s.USERNAME, s.COMMAND, s.OWNERID, s.TADDR, s.LOCKWAIT, s.STATUS, s.SERVER, s.SCHEMA#, s
.SCHEMANAME, s.OSUSER, s.PROCESS, s.MACHINE, s.PORT, s.TERMINAL, UPPER(s.PROGRAM) PROGRAM, s.TYPE, s.SQL_ADDRESS, s.SQL_HASH_VALUE, s.SQL_
ID, s.SQL_CHILD_NUMBER, s.PREV_SQL_ADDR, s.PREV_HASH_VALUE, s.PREV_SQL_ID, s.PREV_CHILD_NUMBER, s.PLSQL_ENTRY_OBJECT_ID, s.PLSQL_ENTRY_SUB
PROGRAM_ID, s.PLSQL_OBJECT_ID, s.PLSQL_SUBPROGRAM_ID, s.MODULE, s.MODULE_HASH, s.ACTION, s.ACTION_HASH, s.CLIENT_INFO, s.FIXED_TABLE_SEQUE
NCE, s.ROW_WAIT_OBJ#, s.ROW_WAIT_FILE#, s.ROW_WAIT_BLOCK#, s.ROW_WAIT_ROW#, s.LOGON_TIME, s.LAST_CALL_ET, s.PDML_ENABLED, s.FAILOVER_TYPE,
s.FAILOVER_METHOD, s.FAILED_OVER, s.RESOURCE_CONSUMER_GROUP, s.PDML_STATUS, s.PDDL_STATUS, s.PQ_STATUS, s.CURRENT_QUEUE_DURATION, s.CLIEN
T_IDENTIFIER, s.BLOCKING_SESSION_STATUS, s.BLOCKING_INSTANCE, s.BLOCKING_SESSION, s.SEQ#, s.EVENT#, s.EVENT, s.P1TEXT, s.P1, s.P1RAW, s.P2
TEXT, s.P2, s.P2RAW, s.P3TEXT, s.P3, s.P3RAW, s.WAIT_CLASS_ID, s.WAIT_CLASS#, s.WAIT_CLASS, s.WAIT_TIME, s.SECONDS_IN_WAIT, s.STATE, s.SER
VICE_NAME, s.SQL_TRACE, s.SQL_TRACE_WAITS, s.SQL_TRACE_BINDS, s.ECID
FROM GV$SESSION S
WHERE
(
s.STATUS = 'ACTIVE'
) AND ( (s.USERNAME is not null) and (NVL(s.osuser,'x') <> 'SYSTEM') and (s.type <> 'BACKGROUND') )
order by "PROGRAM", OWNERID
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedst()+64 call ksedst1() 000000000 ? 000000001 ?
ksedmp()+2176 call ksedst() 000000000 ?
C000000000000D20 ?
4000000004066FE0 ?
000000000 ? 000000000 ?
000000000 ?
ksfdmp()+112 call ksedmp() 000000003 ?
9FFFFFFFFFFEFD60 ?
60000000000BA370 ?
9FFFFFFFFFFF0330 ?
C000000000000999 ?
40000000040AF050 ?
kgeriv()+336 call ksfdmp() 9FFFFFFFFFFF08C0 ?
000000003 ?
9FFFFFFFFFFF0340 ?
60000000000BA370 ?
C000000000000695 ?
4000000009903CE0 ?
000028007 ?
60000000000C6D88 ?
kgesiv()+192 call kgeriv() 60000000000318D0 ?
6000000000032988 ?
4000000001AF8830 ?
000000001 ?
9FFFFFFFFFFF0908 ?
kgesic1()+128 call kgesiv() 60000000000318D0 ?
9FFFFFFFFD3B0CE8 ?
9FFFFFFFFD3B0CF8 ?
000000001 ?
9FFFFFFFFFFF0908 ?
kgherror()+560 call kgesic1() 60000000000318D0 ?
9FFFFFFFFD3B0CE8 ?
0000042DA ? 000000002 ?
9FFFFFFFFD3332F0 ?
$cold_kghfrmrg()+24 call kgherror() 60000000000318D0 ?
0 60000000000315E0 ?
0000042DA ?
9FFFFFFFFD3332F0 ?
60000000000BA370 ?
kghfre()+624 call $cold_kghfrmrg() 60000000000318D0 ?
000000000 ?
60000000000315E0 ?
9FFFFFFFFD333318 ?
000000028 ?
60000000000BA370 ?
C00000000000122B ?
kjzhgigfreep()+192 call kghfre() 60000000000318D0 ?
60000000000315E0 ?
C000001804053D38 ?
001002000 ?
4000000001249AE0 ?
kjzhgigblk()+1808 call kjzhgigfreep() C0000018040531A8 ?
001002000 ?
9FFFFFFFFFFF0940 ?
C000000000001430 ?
400000000703CE00 ?
0000281AB ? 000000000 ?
60000000000C6D88 ?
ksufillglobalblocke call kjzhgigblk() 9FFFFFFFFFFF0FF4 ?
rs()+1936 000000F0F ?
9FFFFFFFFFFF1000 ?
9FFFFFFFFFFF1008 ?
000000001 ?
9FFFFFFFFFFF0964 ?
ksugetblocker()+832 call ksufillglobalblocke 9FFFFFFFFD223F90 ?
rs() 9FFFFFFFFFFF0FF0 ?
60000000000BA370 ?
9FFFFFFFFFFF1B20 ?
C000000000000693 ?
40000000040C29A0 ?
qerfxGCol()+1216 call ksugetblocker() 000000000 ?
9FFFFFFFFFFF1B50 ?
C000000000000715 ?
4000000002F8D7C0 ?
000028627 ?
4000000000F2A360 ?
60000000000315E0 ?
qerfxFetch()+1760 call qerfxGCol() 9FFFFFFFFD30ECF0 ?
9FFFFFFFFFFF1B68 ?
9FFFFFFFFD3D2478 ?
9FFFFFFFFFFF1B68 ?
40000000012BD2A8 ?
4000000001419158 ?
60000000000BA370 ?
C000000000001736 ?
qersoFetch()+2080 call qerfxFetch() C000001870ED53C0 ?
4000000001CCEF30 ?
C000001877BEBC00 ?
000007FFF ?
60000000000BA370 ?
qerjotFetch()+416 call qersoFetch() C000001877BEBC00 ?
4000000001CCEC50 ?
9FFFFFFFFFFF1D00 ?
000007FFF ?
qervwFetch()+368 call qerjotFetch() C000001877BEB450 ?
4000000001CCEC50 ?
9FFFFFFFFFFF1D00 ?
000007FFF ?
qertqoFetch()+800 call qervwFetch() C00000187D6909D0 ?
4000000001CE3F50 ?
9FFFFFFFFD3D28F0 ?
C00000187D6909C8 ?
60000000000BA370 ?
qerpxSlaveFetch()+3 call qertqoFetch() C000001877BEB058 ?
072 000000000 ? 000000000 ?
000007FFF ?
60000000000BA370 ?
C0000000000012AD ?
4000000003D42720 ?
000028361 ?
qerpxFetch()+3504 call qerpxSlaveFetch() 9FFFFFFFFFFF1D80 ?
9FFFFFFFFD3D1390 ?
9FFFFFFFFFFF1D20 ?
9FFFFFFFFD3D1318 ?
9FFFFFFFFFFF1D20 ?
60000000000BA370 ?
9FFFFFFFFFFF22A0 ?
C000000000001E44 ?
opiexe()+23456 call qerpxFetch() C0000018CF8463F8 ?
000000000 ? 002222808 ?
000000001 ?
9FFFFFFFFFFF22C0 ?
60000000000BA370 ?
9FFFFFFFFFFF28C0 ?
4000000002F8B420 ?
kpoal8()+7488 call opiexe() 9FFFFFFFFFFF4560 ?
4000000002BC3640 ?
60000000000C6D90 ?
9FFFFFFFFFFF28E0 ?
60000000000BA370 ?
00003E933 ?
C00000000000122C ?
000000008 ?
opiodr()+2144 call kpoal8() 9FFFFFFFFFFF4C90 ?
C0000000000018B7 ?
9FFFFFFFFFFF9828 ?
9FFFFFFFFFFF45B0 ?
60000000000BA370 ?
4000000002F58B20 ?
kpoodr()+1968 call opiodr() 00000005E ? 000000000 ?
upirtrc()+2272 call kpoodr() 9FFFFFFFFD3D6E60 ?
00000005E ?
60000000000BA370 ?
kpurcsc()+256 call upirtrc() 9FFFFFFFFD3D6E60 ?
00000005E ?
000000000 ?
kpuexecv8()+2784 call kpurcsc() 9FFFFFFFFD3D9DD8 ?
9FFFFFFFFD3D6E7B ?
9FFFFFFFFFFFB100 ?
9FFFFFFFFD3B6308 ?
kpuexec()+2800 call kpuexecv8() 9FFFFFFFFD3D9DD8 ?
9FFFFFFFFD3B6288 ?
9FFFFFFFFD3B6308 ?
000000000 ? 000004000 ?
9FFFFFFFFFFFC100 ?
OCIStmtExecute()+80 call kpuexec() 9FFFFFFFFD3D9DD8 ?
9FFFFFFFFD3B6288 ?
600000000023C728 ?
000000000 ? 000000000 ?
000000000 ? 000000000 ?
000000000 ?
kxfxsStmtExecute()+ call OCIStmtExecute() 9FFFFFFFFD3D9DD8 ?
416 9FFFFFFFFD3B6288 ?
600000000023C728 ?
000000000 ? 000000000 ?
000000000 ? 000000000 ?
000004000 ?
kxfxsExecute()+416 call kxfxsStmtExecute() 9FFFFFFFFD3CA818 ?
C000000000000DA1 ?
9FFFFFFFFD3CA70C ?
kxfxsp()+1152 call kxfxsExecute() 9FFFFFFFFD3CA6D0 ?
9FFFFFFFFFFFC170 ?
MOS ORA-7445 ORA-600[17114] Occured By OMS While Selecting V$SESSION (文档 ID 979103.1)
Applies to:
Oracle Database – Enterprise Edition – Version 10.2.0.4 to 11.1.0.6 [Release 10.2 to 11.1]
Information in this document applies to any platform.
Cause
The cause of this problem has been identified in Bug 9158302 closed as duplicate of Base Bug 8674660:
“Blockers array ” has run past its boundary with a pointer-sized zero.
So, number of blockers becomes inconsistent and lead to a memory corruption.
Bug:8674660 is fixed in RDBMS are fixed in 10.2.0.5 and 11.1.0.7.
Solution
To implement a solution for Bug:8674660, please execute any of the below alternative solutions:
Apply 10.2.0.5 patchset where Base Bug:8674660 is fixed;
OR
Apply 11.1.0.7 patchset where Base Bug:8674660 is fixed;
OR
Check if it’s available the oneoff Patch:8674660 on top of 10.2.0.4 rel. and for your platform.
微信扫一扫，打赏作者吧～
对不起，这篇文章暂时关闭评论。