Re: sort_area_size / sort_area_retained_size

Stick 'em up high. If you've got lots of disk sorts, the sort_area_size is too low. Throw some more numbers at it, and they should go away -or most of them at any rate.

Bear in mind that until a user starts actually doing a sort, s/he doesn't actually possess any sort_area_size at all, whatever the parameter file might say. It's a limit to which the thing can grow on demand -and once the demand's finished, it shrinks back down.

10Mb sounds like a good starting point to me.

Regards
HJR "Stan" <stan0074_at_yahoo.com> wrote in message news:3CABDE59.8080404_at_yahoo.com...
> actually we have a hybrid of oltp and dss in a database and right now i
> have 1mb for sort_area_size and 512k for sort_area_retained_size.
>
> markag wrote:
>
> > Stan wrote:
> > > I see lots of disk sorts on my statpack reports, so how do i
determine
> > > the average sort_area_size and sort_area_retained_size that needs to
> > > increased based on concurrent disk sorts ?
> > > Any advise!
> > > thanks in advance, Stan
> >
> >
> >
> > What are they now? recommendations for OLTP systems can be 64K to 256K;
> > Batch processes are higher, 20-50M. My OLTP setting is actually 2M.
> >
> > You just need to play with it...
> >
> > This from an Oracle book I am reading....it really depends on # of
> > users, total physical memory, size of the process being performed,
> > etc. Total Physical Memory is the key though. You usually want Oracle
> > to use as much memory as possible without forcing swapping to disk at
> > the OS level.
> >
> > Anyway, the two params should be set to the same value usually.
> >
> >
> >
> > --
> > Posted via dBforums
> > http://dbforums.com
> >
>
Received on Thu Apr 04 2002 - 00:21:59 CST