ORA-600 [kgh_heap_sizes:ds]/[kghGetHpSz1] Observed in Alert Log
(Doc ID 741135.1)
Last updated on APRIL 06, 2020
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.3 to 10.2.0.3 [Release 10.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
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
in the stack the note is unlikely to provide a resolution.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document