Excess Shared Pool Memory Use / ORA-4031 Due To Large "KTC Latch Subh" Allocation and Dequeues
(Doc ID 2281917.1)
Last updated on FEBRUARY 22, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.4 and laterOracle 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.
Symptoms
Errors reported in the alert log:
ORA-04031: unable to allocate 544 bytes of shared memory ("shared pool","unknown object","sga heap(3,1)","KGLHD")
ORA-04031: unable to allocate 192 bytes of shared memory ("shared pool","unknown object","KTC latch subh","KTCCC OBJECT")
Or unusually large allocations to "KTC latch subh" shown in the shared pool:
TOP 20 MEMORY USES ACROSS SGA HEAP 1 - 6
----------------------------------------------
"KTC latch subh " 2940 MB 64%
"free memory " 1045 MB 23%
"SQLA " 69 MB 1%
"KWQDL deq log " 67 MB 1%
Also, increases in "KTC latch subh" can be seen following usage of DBMS_AQ.DEQUEUE.
Patch for Bug 18850278 does not provide relief.
Changes
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 |