ORA-04031 With Leak in "OBJ STAT MEMO" Allocations Seen in V$SGASTAT on 10.2.0.5
(Doc ID 1350050.1)
Last updated on FEBRUARY 19, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.5 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata 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.
The following symptoms are required for this article to be applicable :-
a) The database version is specifically 10.2.0.5
b) The database sees many DROP/CREATE activities
c) In ORA-4031 trace files, we will see subpool information similar to :-
Memory Utilization of Subpool 1
Allocation Name Size
"free memory " 107844008
"obj stat memo " 413473896 <==== large allocations
There might be many subpools, but the pattern to look for is that we see plenty of free memory and high values for allocation "obj stat memo"
d) The following SQL queries will return results that continually increase :-
f) Using _disable_objstat_del_broadcast=false stops the ORA-04031 errors and the SQL in (D) and (E) no longer shows an increase on "obj stat memo"
This article is solely written for 10.2.0.5. If any other version or PSR is being used the article will not be appropriate. For versions prior to10.2.0.5, <Note.9737897.8> can be considered but this is beyond the scope of this document.
The database might have been patched or upgraded to 10.2.0.5 but the problem can also be seen on a database that has only ever existed as 10.2.0.5.
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