Re: PGA_AGGREGATE_TARGET question

From: Anurag Varma <avdbi_at_hotmail.com>
Date: Thu, 14 Aug 2003 02:45:37 GMT
Message-ID: <lJC_a.17941$w42.12867@news02.roc.ny>

"Bob Maggio" <zekmoeNoSpam_at_nycap.@rr.@com> wrote in message news:2XB_a.92791$wk4.44475_at_twister.nyroc.rr.com...
> We are moving to PGA_AGGREGATE_TARGET from sort_area sizes etc. However, I
> am unsure about sizing it. If I size it too large, is there any drawbacks,
> aside from some wasted memory? I'd rather err on the side of caution if
> possible. I've heard that 1m per connection is a good starting point. If I
> average 650 concurrent sessions, with maybe 10 to 20 active ones at any
> given moment, is setting it to 650m ok? I've used this in test DBs but
> haven't yet tried it on PROD ones. This is a 9i, not 9iR2 DB.
> Thanks for any rule of thumb advice.
> Bob
>
>

Sizing pga_aggregate_target would depend on couple of factors. One obvious being the amount of memory available.
Take a look around in metalink. There are couple of notes out there giving you an idea how to estimate the size for the first time. After that you can take a look around in v$pgastat and you would get to see Oracles nice advice view teeling you what you want to see.

Anurag Received on Wed Aug 13 2003 - 21:45:37 CDT