ORA-04031: ("shared Pool".."KKSSP^nnnn","kglseshtSegs")
(Doc ID 2151847.1)
Last updated on APRIL 01, 2024
Applies to:
Oracle Database Cloud Service - Version N/A and laterOracle Database - Enterprise Edition - Version 12.1.0.1 to 12.2.0.1 [Release 12.1 to 12.2]
Oracle Database Cloud Schema Service - Version N/A 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
Information in this document applies to any platform.
Symptoms
There are 2 types of symptoms for this issue:
1. A session hits an ORA-4031:
- the ORA-4031 is received when trying to allocate memory tagged with "KKSSP^nnnn" where "nnnn" is the session number
- the typical allocation failure is on "kglseshtSegs"
- for the session that is allocating the memory, we see that it has lots of KGL pins acquired against the same object, and that object is a synonym. (this is visible in the incident trace)
- kkdltob() will typically be on the stack.
OR
2. Even without ORA-4031, there is evidence "KKSSP^nnnn" type of memory is consuming lots of shared pool memory.
Example:
ORA-04031: unable to allocate ... bytes of shared memory ("shared pool","unknown object","KKSSP^nnnn","kglseshtSegs")
Call stack :
...kkscscid_auc_eval->kksauc->kkdltob->kglpin->kglpnal->kglSessionHashInsert->kghssggr->kghalf
Information on most relevant allocations, from incident trace file:
==============================================
TOP 20 MEMORY USES ACROSS SGA HEAP 1 - 6
----------------------------------------------
"KKSSP " 12 GB 49% <<<<<<<
...
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 |
| Cause |
| Solution |
| References |