RE: pga_aggregate_target

  • From: "Ruth Gramolini" <rgramolini@xxxxxxxxxxxxxxx>
  • To: <oracle-l@xxxxxxxxxxxxx>
  • Date: Fri, 3 Sep 2004 15:53:47 -0400

When we were experencing rowcache waits and extreme slowness OWS suggested
that we increase the PAT from 100000000 to 1000000000 along with increasing
the size of the shared_pool, etc.  It worked and we have left it this way
since then.  It helped with the rowcache problem.  I can look up the info
from the TAR when I return on Tuesday if you send me an email offlist.

Ruth Gramolini
Oracle DBA
Vermont Department of Taxes
Phone 802-828-5708
Email rgramolini@xxxxxxxxxxxxxxx <mailto:rgramolini@xxxxxxxxxxxxxxx>  

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Peter Barnett
Sent: Thursday, September 02, 2004 9:42 AM
To: Oracle-l
Subject: pga_aggregate_target

Has anyone used this parameter in 9i (

I have a vended application with multiply nested
unions and select distincts.  The vendor has cleaned
up some of the worst queries but it is still very
sloppy and ineffcient.

The server is dedicated to this application's
database. It has lots of RAM (12G) and CPUs (4).  It
hammers the CPUs pretty hard, as much as 100%
utilization during prime user time.  With everything
taken into account, it barely uses 2G of memory.  The
best conclusion I can draw from mulitple analysis of
statspack output is tune the application which is not

Any thoughts or experience with this parameter?

Pete Barnett
Lead Database Administrator
The Regence Group

Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
To unsubscribe - mailto:oracle-l-request@xxxxxxxxxxxxx&subject=unsubscribe
To read recent messages -

To unsubscribe - mailto:oracle-l-request@xxxxxxxxxxxxx&subject=unsubscribe 
To search the archives -

Other related posts: