Re: Actually PGA allocated > PGA_AGGREGATE_TARGET ?
- From: Niall Litchfield <niall.litchfield@xxxxxxxxx>
- To: Lu.Jiang@xxxxxxxxxxxx
- Date: Mon, 10 Aug 2009 19:02:33 +0100
you don't share your sql. However the key may well be in the word "attempts"
PGA_AGGREGATE_TARGET isn't a hard limit, though 30% above is somewhat
surprising for a target of 1g.
Niall
On Mon, Aug 10, 2009 at 6:56 PM, Jiang, Lu <Lu.Jiang@xxxxxxxxxxxx> wrote:
> Hi all,
>
>
>
> 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
>
> 1,073,741,824.00
>
> bytes
>
> aggregate PGA auto target
>
> 85,053,440.00
>
> bytes
>
> global memory bound
>
> 107,366,400.00
>
> bytes
>
> total PGA inuse
>
> 984,952,832.00
>
> bytes
>
> total PGA allocated
>
> 1,259,997,184.00
>
> bytes
>
> maximum PGA allocated
>
> 1,347,652,608.00
>
> bytes
>
>
>
> Thanks,
>
> Lu
>
--
Niall Litchfield
Oracle DBA
http://www.orawin.info
Other related posts:
