Database Instance Crash After ORA-4031 ("shared pool","unknown object","KGSKI schedule","KGKP cache") (Doc ID 1908421.1)

Last updated on JUNE 27, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.3 to 11.2.0.4 [Release 11.2]
Information in this document applies to any platform.
ORA-4031 ("shared pool","unknown object","KGSKI schedule","KGKP cache")
ORA-4031 [nnn] [shared pool] [unknown object] [KGSKI schedule] [KGKP cache]

Symptoms

Database instance crash after ORA-4031 ("shared pool","unknown object","KGSKI schedule","KGKP cache")

The database instance alert log would report the ORA-4031 [KGKP cache], followed by the instance crash:

Errors in file /u01/app/oracle/diag/rdbms/<database name>/<instance name>/trace/<instance name>_dbrm_pppp.trc  (incident=680300):
ORA-04031: unable to allocate nnn bytes of shared memory ("shared pool","unknown object","KGSKI schedule","KGKP cache")
Incident details in: /u01/app/oracle/diag/rdbms/<database name>/<instance name>/incident/incdir_680300/<instance name>_dbrm_pppp_i680300.trc
<date and time>
Dumping diagnostic data in directory=[cdmp_20140709203001], requested by (instance=N, osid=pppp (DBRM)), summary=[incident=680300].
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /u01/app/oracle/diag/rdbms/<database name>/<instance name>/trace/<instance name>_dbrm_pppp.trc:
ORA-04031: unable to allocate nnn bytes of shared memory ("shared pool","unknown object","KGSKI schedule","KGKP cache")
DBRM (ospid: pppp): terminating the instance due to error 4031
System state dump requested by (instance=N, osid=pppp (DBRM)), summary=[abnormal instance termination].
System State dumped to trace file /u01/app/oracle/diag/rdbms/<database name>/<instance name>/trace/<instance name>_diag_98129.trc
<date and time>
ORA-1092 : opitsk aborting process
<date and time>
License high water mark = 1970
Instance terminated by DBRM, pid = pppp

 

The trace file would have the following:

Begin 4031 Diagnostic Information
=================================
The following information assists Oracle in diagnosing
causes of ORA-4031 errors.  This trace may be disabled
by setting the init.ora _4031_dump_bitvec = 0
=====================================
Allocation Request Summary Informaton
=====================================
Current information setting:  04014fff
  SGA Heap Dump Interval=3600 seconds
  Dump Interval=300 seconds
  Last Dump Time=07/09/2014 20:29:24
  Dump Count=1
Allocation request for:       KGKP cache
  Heap: 0xdd75f7ec0, size: 70144
******************************************************
HEAP DUMP heap name="sga heap"  desc=0x60001190
 extent sz=0x9800 alt=248 het=32767 rec=9 flg=-126 opc=0
 parent=(nil) owner=(nil) nex=(nil) xsz=0x1 heap=(nil)
 fl2=0x60, nex=(nil)
 ds for latch 1: 0x60057460                                 
 ds for latch 2: 0x60060d28                                 
 ds for latch 3: 0x6006a5f0                                 
 ds for latch 4: 0x60073eb8                                 
 ds for latch 5: 0x6007d780                                 
 reserved granule count 0 (granule size 134217728)
******************************************************
HEAP DUMP heap name="KGSKI schedule"  desc=0xdd75f7ec0
 extent sz=0x1040 alt=32767 het=32767 rec=9 flg=2 opc=0
 parent=0x60001190 owner=(nil) nex=(nil) xsz=0x8000000 heap=(nil)
 fl2=0x20, nex=(nil), dsxvers=1, dsxflg=0x0
 dsx first ext=0xbe13860
 Subheap has 106952 bytes of memory allocated

 

Stack trace:

skdstdst ksedst1 ksedst ksm_4031_dump ksmasg kghnospc kghalp kgkploinst kgskreset kgskirefpl kskreload
kskcicdbrm ksbmsg ksbcti ksbabs ksbrdp opirip opidrv sou2o opimai_real ssthrdmain main libc_start_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