SMON Experiencing ORA-4030 Errors Eventually Causing The Database Is Crash (Doc ID 1484676.1)

Last updated on AUGUST 17, 2012

Applies to:

Oracle Server - Enterprise Edition - Version 11.2.0.2 and later
Information in this document applies to any platform.

Symptoms

The instance terminates due to the following errors:

 

ORA-00603: ORACLE server session terminated by fatal error
ORA-24557: error 4030 encountered while handling error 4030; exiting server process
ORA-04030: out of process memory when trying to allocate 8168 bytes (callheap,kcbtmal allocation)
ORA-04030: out of process memory when trying to allocate 8168 bytes (callheap,kcbtmal allocation)
ORA-04030: out of process memory when trying to allocate 8168 bytes (callheap,kcbtmal allocation)
opidrv aborting process SMON ospid (37814326) as a result of ORA-603

 

From a heap dump of the SMON trace we see we can see that the "kod objects" and "koi korfp" are eating up the session heap.


---> HEAP DUMP heap name="koh-kghu sessi"  desc=110a9af60
             Type           Count             Sum         Average
             ~~~~           ~~~~~             ~~~         ~~~~~~~
         freeable          756773     12356551896        16327.95
             perm               1              80           80.00

BreakDown
~~~~~~~~~
             Type           Count             Sum         Average Percent
             ~~~~           ~~~~~             ~~~         ~~~~~~~ ~~~~~~~
  koi korfc                135877      2218599656        16328.00  17.95
  kod objects              166732      2722384816        16327.91  22.03 <<<<------
  koi korfp                194379      3173820312        16328.00  25.69 <<<<------
  kopo object              166195      2713609592        16327.87  21.96
  koh korfp                 67682      1105111696        16328.00   8.94
  kodpunp koplds             6695       109315960        16328.00   0.88
  kod cdsalloc:cd           11578       189045584        16328.00   1.53
  kol varray                 1252        20442656        16328.00   0.17
  kodpunp lds                6020        98294560        16328.00   0.80
  kodpunp kohldsc             363         5927064        16328.00   0.05
  perm                          1              80           80.00   0.00

Total = 12356551976 bytes     12066945.29k        11784.13M 

 
The stack trace will be similar to the following:

skdstdst <- ksedst1 <- ksedst <- dbkedDefDump <- ksedmp <- ksdxfdmp <- ksdxcb <- sspuser <- 47dc <- kxsFreePersistentHeap <- kxsCloseXsc <- kksCloseCursor <- opicca <- opiclo <- opicls <- opiodr <- rpidrus <- skgmstack <- rpidru <- rpiswu2 <- rpidrv <- rpicls <- kqlclo1 <- kqlclo <- ktmmon <- ktmSmonMain <- ksbrdp <- opirip <- opidrv <- sou2o <- opimai_real <- ssthrdmain <- main <- start

 

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