MEMORY LEAK 'KTC LATCH SUBH' ON AQ DEQUEUE
(Doc ID 2760358.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 18.8.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
ORA-04031: unable to allocate 40 bytes of shared memory ("shared pool","select obj#,index# from oid$...","KGLH0^34cbe0ff","kglHeapInitialize:temp")
Bug 31666684 - MEMORY LEAK 'KTC LATCH SUBH' ON AQ DEQUEUE
ORA-4031 seen while dequeuing a large number of AQ messages in a transaction. "KTC latch subh" appears to keep growing in V$SGASTAT
Changes
ORA-4031 seen while dequeuing a large number of AQ messages in a transaction."KTC latch subh" appears to keep growing in V$SGASTAT
SQL> SELECT POOL,NAME,ROUND(BYTES/1024/1024,2) MB FROM V$SGASTAT where NAME='KTC latch subh';
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 |