Re: High TEMP tablespace IO rate

Actually not true, in the strictest sense.

If you say sort area size should be 1m, your users acquire a very small PGA which, when sorts begin, *grows* to be 1m. When the sorts finish, the PGA shrinks back to whatever your sort area retained size is set to.

It is therefore possible to allocate users a much larger PGA than the pure numbers might suggest, provided they don't all connect at the same time and simultaneously start doing sorts!

Regards
HJR

--
--------------------------------------------------------------------------
Opinions expressed are my own, and not those of Oracle Corporation
Oracle DBA Resources:               http://www.geocities.com/howardjr2000
--------------------------------------------------------------------------



"John Jones" <john.jones_at_duke.edu> wrote in message
news:8pqf8u$kkq$1_at_news.duke.edu...


> You have to be careful with SORT_AREA_SIZE.  Each user that logs in gets

> that amount of memory allocated to them, so if you have lots of users, you

> have to have lots of memory.

>

> --

> John Jones

> Senior Oracle DBA

> Duke University OIT

> john.jones_at_duke.edu

> "Brian Peasland" <peasland_at_edcmail.cr.usgs.gov> wrote in message

> news:39BFC0B0.9A9691EA_at_edcmail.cr.usgs.gov...

> >

> >

> > > Sounds like you are doing lots of sorts and/or index builds.  You may

 be


> > > able to minimize sorting via indexes.  Get the SQL from v$sql with the

> > > highest number of sort i/o's, and perform explain plans on it.

> >

> > One could also increase the SORT_AREA_SIZE to cause more sorts to be

> > performed in memory rather than on disk.

> >

> > HTH,

> > Brian

> >

> >

> > --

> > ========================================

> > Brian Peasland

> > Raytheons Systems at

> >   USGS EROS Data Center

> > These opinions are my own and do not

> > necessarily reflect the opinions of my

> > company!

> > ========================================

>

>