My Oracle Support Banner

PGA Memory Allocation Exceeds MEMORY_MAX_TARGET. (Doc ID 604080.1)

Last updated on FEBRUARY 01, 2022

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 11.1]
Information in this document applies to any platform.


When MEMORY_MAX_TARGET is set, some views are showing that PGA is actually using more memory than the value of MEMORY_MAX_TARGET :

SQL> select name,value from v$system_parameter
where name in (

------------------------------ -------------
sga_max_size 314572800
shared_pool_size 0
large_pool_size 0
java_pool_size 0
streams_pool_size 0
sga_target 0
memory_target 314572800
memory_max_target 314572800
db_cache_size 0
pga_aggregate_target 0
workarea_size_policy AUTO

SQL> select * from v$pgastat;

------------------------------------------ -------------- ------------
aggregate PGA target parameter 71303168 bytes
aggregate PGA auto target 4456448 bytes
global memory bound 25165824 bytes
total PGA inuse 234960896 bytes
total PGA allocated 930527232 bytes
maximum PGA allocated 968351744 bytes
total freeable PGA memory 24969216 bytes
process count 38
max processes count 43
PGA memory freed back to OS 28450226176 bytes
total PGA used for auto workareas 0 bytes
maximum PGA used for auto workareas 24916992 bytes
total PGA used for manual workareas 0 bytes
maximum PGA used for manual workareas 536576 bytes
over allocation count 2195708
bytes processed 113574183936 bytes
extra bytes read/written 9022009344 bytes
cache hit percentage 93 percent
recompute count (total) 2195708


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.