ORA-4031 Against Shared Pool With Huge Memory Allocations To KGLH0
(Doc ID 1621829.1)
Last updated on FEBRUARY 18, 2019
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 to 18.104.22.168 [Release 11.2]
Oracle Database - Enterprise Edition - Version 22.214.171.124 to 126.96.36.199 [Release 11.2]
Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Information in this document applies to any platform.
Getting ORA-4031 errors against shared pool when in one subpool the KGLH0 heap is reaching GBs of memory. For example:
<Patch 13456573>, <Patch 17804522>, <Patch 17606989> and <Patch 14770516> containing fixes for bugs:
<Bug 13456573> - Many child cursors / ORA-4031 with large allocation in KGLH0 using extended cursor sharing
<Bug 13054713> - High version_count / ORA-942 on statements where DDLs happen over the objects.
<Bug 14176247> - Many child cursors using Adaptive Cursor Sharing with binds (due to BIND_EQUIV_FAILURE)
<Bug 14770516> - SGA memory leak in KGLH0 under shared pool
were installed with no results.
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