ORA-04031 With Leak in "OBJ STAT MEMO" Allocations Seen in V$SGASTAT on

(Doc ID 1350050.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Server - Enterprise Edition - Version: and later   [Release: 10.2 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
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 :-

select * from v$sgastat where name = 'obj stat memo';
select count(distinct fts_objd) from x$ksolsfts;

e) The following SQL will show a continual steady increase for "obj stat memo"

(SELECT NAME, BYTES/(1024*1024) MB
WHERE POOL = 'shared pool'

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  If any other version or PSR is being used the article will not be appropriate.  For versions prior to10.2.0.5, <> can be considered but this is beyond the scope of this document.


The database might have been  patched or upgraded to but the problem can also be seen on a database that has only ever existed as


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms