RE: Actually PGA allocated > PGA_AGGREGATE_TARGET ?
Date: Mon, 10 Aug 2009 13:10:21 -0500
Key words that help in this is that it's a TARGET not a LIMIT. And as it says it "attempts" to stay below this. It can and will (as in your case) accede this.
It looks like at one time oracle needed 1.3G and more recently it needed 1.2G but right now is using .9G. From this as a SWAG I'd say you should set PGA_AGGREGATE_TARGET to about 1.2G. The issue is that once you go above the target, I think it's SMON that will get excited about trying to bring the allocated back done. This would cause a little be more activity at the system level. However this is unlikely to be a big deal.
Ric Van Dyke
March 7 - 11, 2010
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Jiang, Lu Sent: Monday, August 10, 2009 1:56 PM
To: Oracle-L Freelists
Subject: Actually PGA allocated > PGA_AGGREGATE_TARGET ?
The following is my query result against v$pgastat view. PGA_AGGREGATE_TARGET is set to 1G. According to Oracle' documentation, Oracle should attempts to keep the amount of private memory below the PGA_AGGREGATE_TARGET specified. But from the following it looks Oracle allocated 1.2G PGA memory, and the maximum PGA allocated is 1.3GB which is far above 1G (PGA_AGGREGATE_TARGET), I am confused. Could anyone share some light on this?
aggregate PGA target parameter
aggregate PGA auto target
global memory bound
total PGA inuse
total PGA allocated
maximum PGA allocated
LuReceived on Mon Aug 10 2009 - 13:10:21 CDT