ORA-600 [kgh_heap_sizes:ds]/[kghGetHpSz1] Observed in Alert Log

(Doc ID 741135.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 10.2]
Information in this document applies to any platform.
*** Checked for relevance on 26-Oct-2012 ***


The following symptoms have been attributed to this issue :-

a) The following errors are seen in the alert log :-

ORA-00600: internal error code, arguments: [kgh_heap_sizes:ds]
ORA-00600: internal error code, arguments: [kghGetHpSz1]
ORA-07445: exception encountered: core dump [] [] [] [] [] []

It should be noted that these are very generic and can be seen in many bugs so the following
symptoms also need to be encountered.  To be relevant to this article one or more of these
errors are written into the same UDUMP trace file.

b) The 'Current SQL' statement is not considered specific i.e. it could be an INSERT/UPDATE
or it may be that the trace file reports :-

No current SQL statement being executed.

c) The call stack trace will be similar to :-

kghnerror <- kgh_heap_sizes <- kxsDump1 <- kxsDump
<- kxsDumpCursor <- kxsDumpCursors <- curdmp <- ksudps <- ksedmp
<- ssexhd <- 000044BC <- kdtlo2l_opn_to_ldef <- insLoadRow <- insfch
<- insdrv <- inscovexe <- insExecStmtExecIniE <- ngine <- insexe
<- opiexe <- kpoal8 <- opiodr <- ttcpip <- opitsk
<- opiino <- opiodr <- opidrv <- sou2o <- opimai_real <- main <- start

The key function for this article to be considered is 'kdtlo2l_opn_to_ldef', if this is not seen
in the stack the note is unlikely to provide a resolution.



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