I would like to manually control the amount of pga my session uses or
is allowed to use

/ from 0 to 500m

Please could anyone on advise on parameters that I need to manipulate


cheers
Chris B

PS I want to do this so that I can force use of temp so that I can
compare results on a fair basis between runs / a bit like alter system
flush buffer_cache effect on sga;

On Sep 6, 8:19*am, dba cjb <chris.br... (AT) providentinsurance (DOT) co.uk>
wrote:
You should be able to achieve this with an alter session by setting
sort_area_size and setting workarea_size_policy to manual, but it
depends on your version/patch level, your pga_aggregate_target, what
exactly you are doing, and probably some mysterious stuff.

http://hoopercharles.wordpress.com/2...te_target-set/
is interesting.

jg
--
@home.com is bogus.
http://blogs.computerworlduk.com/the...ened/index.htm

On Sep 6, 11:19*am, dba cjb <chris.br... (AT) providentinsurance (DOT) co.uk>
wrote:
Even though you can influence the amount of PGA a session is initially
given via various settings such as sort_area_size and hash_area_size
the fact of the matter is that it is the code being executed that
determines how much PGA a session will need and there are no public
parameters that allow you to limit this. If the code uses pl/sql
collections and types and loads data into the collections then Oracle
will keep taking memory to hold the data up to any Oracle and OS
platform limitations that exist.

On Windows Oracle sessions run as threads within the Oracle
executiable space.

HTH -- Mark D Powell --