Re: pga_aggregate_target plus sort_area_size set in init.ora

You don't need to delete sort_area_size to use the pga_aggregate_target. You need only make sure that you have set workarea_size_policy to AUTO.

It is possible that it has been left there because some sessions invoke

    alter session set workarea_size_policy = manual;

In the absence of a specific value, this would cause such sessions to fall back to 64K

-- 
Regards

Jonathan Lewis

http://www.jlcomp.demon.co.uk

http://www.jlcomp.demon.co.uk/faq/ind_faq.html
The Co-operative Oracle Users' FAQ

http://www.jlcomp.demon.co.uk/seminar.html
Optimising Oracle Seminar - schedule updated May 1st


"Johannes" <johannes_at_merckle.de> wrote in message
news:2kfk5aF1oqsqU1_at_uni-berlin.de...


> Hi all!

>

> I hava an installation of Oracle 9.2 with pga_aggregate_target set in

> init.ora.

> As this parameter replaces e.g. sort_area_size and hash_area_size and

other


> pga relevant parameters in init.ora (in dedicated server systems),

> I don't know why my predecessor let this parameters set in init.ora.

> They seem to be used setting this memory pools, becaus using "show

parameter


> xxx"

> prompts the assigned values.

> I think I have to delete this parameters (sort_area_size,... and all other

> pga relevant parameters)

> to handle pga_aggregate_target correct.

> What do you think about?

> Thank you all!

>

> Johannes

>

>