ORA-600[17059] AND 600[KKSHEQD0] REPORTED INTO SAME TRACE FILE AND SESSIONS SEEM TO HANG

(Doc ID 784845.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.4 [Release 10.2]
Information in this document applies to any platform.

***Checked for relevance on 22-Jan-2014***

Symptoms

This article actually covers two bugs which due to their nature might be faced at the
same time if the following symptoms are seen :-

a) Alert log reports both ORA-600 errors under the same trace file e.g. :-

Errors in file /xxxxxxxx/XXXX_j000_16698.trc
(incident=328329):
ORA-00600: internal error code, arguments: [17059], [0x23BF437C8], [0x23BF43190]
, [0x24B9EA9A8], []
Incident details in: /xxxxxxxx/XXXX_j000_16698_i328329.trc
Errors in file /xxxxxxxx/XXXX_j000_16698.trc
(incident=328330):
ORA-00600: internal error code, arguments: [kksheqd0], [0x1C71C38E8],
[0xB38F0000000239], []

b)   There is no specific SQL associated with the 600[17059] trace but the incident trace file
might report a stack trace similar to the following :-

Function List (to Full stack) (to Summary stack)
kgeade <- kgeriv_int <- kgeriv <- kgesiv <- kgesic3 <- kgltba <- kglhdgc <- kglget
<- kxsGetLookupLock <- kksfbc <- kkspsc0 <- kokapvpr <- PGOSF460_kokacau
<- kokasuc <- kokavpr <- kokageti <- kokdlod <- kodclod <- kocobld <- kocgpn2 <- kocgpn
<- kocpin <- kohaii <- kociih <- koionew2 <- koionew <- pefiadtargs <- pefpargs <- pefccal
<- pefcal <- pevm_FCAL <- pfrinstr_FCAL <- pfrrun_no_tool <- pfrrun <- plsql_run
<- peicnt <- kkxexe <- opiexe <- opiodr <- PGOSF150_rpidrus <- skgmstack
<- rpidru <- rpiswu2 <- rpidrv <- rpiexe <- kkjex1e <- kkjsexe <- kkjrdp <- opirip
<- opidrv <- sou2o <- opimai_real <- ssthrdmain <- main <- libc_start_main <- start

c) As with the 600[17059] no specific SQL is associated with the 600[kksheqd0] error.  Again
a stack trace might be similar to the following :-

Function List (to Full stack) (to Summary stack)
ksedmp <- ksupop <- opiodr <- PGOSF150_rpidrus <- skgmstack
<- rpidru <- rpiswu2 <- rpidrv <- rpiexe <- kkjex1e
<- kkjsexe <- kkjrdp <- opirip <- opidrv <- sou2o
<- opimai_real <- ssthrdmain <- main <- libc_start_main <- start

d) NLS_LENGTH_SEMANTICS=CHAR is set within the init/spfile

e) Session 'hangs' are reported around time of the ORA-600's, the main wait event that is seen
is 'kksfbc child completion'

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