My Oracle Support Banner

Size of State Objects (ktlbk) Keeps Increasing Till 4031 is Thrown (Doc ID 1638733.1)

Last updated on MAY 19, 2021

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.3 and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

Many 4031 errors are reported:
ORA-04031: unable to allocate 32 bytes of shared memory ("shared pool","unknown object","KGLH0^9f4ac8c0","kglHeapInitialize:temp")
ORA-04031: unable to allocate 32 bytes of shared memory ("shared pool","unknown object","KGLH0^ae1da3c","kglHeapInitialize:temp")

The database is running, but the state objects in the shared pool keep on increasing:

select  bytes, sysdate from v$sgastat where name like 'state o%';

425968 20/03/2014 12:58:02
37831768 20/03/2014 12:59:17
51050968 20/03/2014 12:59:48
60596008 20/03/2014 13:00:21
95251048 20/03/2014 13:02:13
123779248 20/03/2014 13:03:46
157915888 20/03/2014 13:05:59
216268288 20/03/2014 13:10:45
303839008 20/03/2014 13:15:56
365693848 20/03/2014 13:20:01
399075568 20/03/2014 13:21:43

As one can be seen from the heap dump you see that these are from the "ktlbk" (List of blocks) state objects.

 

Changes

Nothing

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.