If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

ok what happened if the user need more than 60M??? can we set the autoextend on for TEMP tablespace??? It seem like we can't b/c I tried the below scripts and it still set autoextend of after I run the script below:

Because if i have a Temporary LMT with uniform size say 10M. Then even for a small sort operation requiring say 64k of space an extent of 10M will be allocated.

Where as in system managed LMT the first few extents allocated would of 64k, then 1M, then 8M and so on. So for a small sort of 64k only one extent of 64k will be allocated instead on 10M as in case of uniform sized Temporary LMT. And of course for larger sorts the extent size will grow accordingly from 64k to 1M to 8M and so on.

Last edited by adewri; 04-16-2003 at 11:03 AM.

Amar"There is a difference between knowing the path and walking the path."

But in 9i where i'm using workarea_size_policy=auto and setting a value of pga_aggregate_target. Then the sort_area_size wont come into picture as the amount of space to be allocated would be controlled by ORACLE automatically depending upon the value of pga_aggregate_target and the amount of memory required for sorting.

Cheers...

PS: Advices are welcome as i'm still testing on these grounds.

Amar"There is a difference between knowing the path and walking the path."

Originally posted by adewri Where as in system managed LMT the first few extents allocated would of 64k, then 1M, then 8M and so on. So for a small sort of 64k only one extent of 64k will be allocated instead on 10M as in case of uniform sized Temporary LMT. And of course for larger sorts the extent size will grow accordingly from 64k to 1M to 8M and so on.

Did you test this behaviour or you are talking on theoritical/documentation grounds ?