Loss of Connection, ORA-3113 and ORA-7445 [kghalf()+1616] (Doc ID 1069078.1)

Last updated on FEBRUARY 07, 2014

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.2.0.1 [Release 10.1 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 29-Aug-2013***

Symptoms

The following errors are seen in the alert log:

Errors in file /u02/app/oracle/admin/sid/bdump/sid_s000_65016.trc:
ORA-00600: internal error code, arguments: [17114], [0x2000000002036C20],
[], [], [], [], [], []
Wed Dec 9 10:43:08 2009
Errors in file /u02/app/oracle/admin/sid/bdump/sid_s000_65016.trc:
ORA-00600: internal error code, arguments: [17114], [0x2000000002036C20],
[], [], [], [], [], []
Wed Dec 9 10:43:08 2009
Trace dumping is performing id=[cdmp_20091209104308]
Wed Dec 9 10:43:34 2009
found dead shared server 'S000', pid = (38, 2)
Wed Dec 9 10:46:32 2009

 - OR -

Thu Dec 10 04:14:55 2009
Errors in file /u02/app/oracle/admin/sid/bdump/sid_s002_13481.trc:
ORA-07445: exception encountered: core dump [kghalf()+848] [SIGSEGV]
[unknown code] [0x6000000A002A2700] [] []
Thu Dec 10 04:15:38 2009
Errors in file /u02/app/oracle/admin/sid/bdump/sid_s002_13481.trc:
ORA-07445: exception encountered: core dump [kghalf()+1616] [SIGSEGV]
[unknown code] [0x6000000A002A26F0] [] []
ORA-07445: exception encountered: core dump [kghalf()+848] [SIGSEGV]
[unknown code] [0x6000000A002A2700] [] []
Thu Dec 10 04:16:42 2009
found dead shared server 'S002', pid = (40, 1)
Thu Dec 10 05:25:43 2009


The failing SQL may rerun succesfully after receiving the errors.

The trace file shows "pga heap" is corrupted, for example:


EXTENT 10 addr=0x2000000002040010
Chunk 2000000002040020 sz= 3392 perm "perm " alo=3392
Chunk 2000000002040d60 sz= 1248 free " "
Chunk 2000000002041240 sz= 2072 freeable "kopolal dvoid "
Chunk 2000000002041a58 sz= 20592 free " "
Chunk 2000000002046ac8 sz= 32848 freeable "kgh stack "
Chunk 200000000204eb18 sz= 320 freeable "KSXP osd connec"
Chunk 200000000204ec58 sz= 232 freeable "KSXP connection"
Chunk 200000000204ed40 sz= 192 freeable "New kjctte entr"
Chunk 200000000204ee00 sz= 192 freeable "New kjctte entr"
Chunk 200000000204eec0 sz= 192 freeable "New kjctte entr"
Chunk 200000000204ef80 sz= 3904 freeable "Alloc environm " ds=0x60000000002e0320
Chunk 200000000204fec0 sz= 320 freeable "KSXP osd connec" EXTENT 11 addr=0x2000000002030010
Chunk 2000000002030020 sz= 27648 BAD MAGIC NUMBER IN NEXT CHUNK (C0B3000A00000049)


The call stack in the trace file may be similar to:

... kghalf kfioRqSetCreate kfioSubmitIO kfioRequest ksfd_osmio ksfdread1 ksfdread kcfrbd kcbzib kcbget ktbxchg kdifind kdiins0 kdiinsp kauxsin insidx insrow insdrv inscovexe ...


Having the following events set will then show the result below:


The trace now shows parameters to qcuErroep pos = 0xa (the corrupting value in the other traces) and error 911.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms