Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Use of TEMP tablespace other than sorting
Decrease value of hash_area_size to 4M or drop recreate the temp tablespace with uniform extent of at least 8M (or 8 * n M).
I believe thats where the problem lies.
Anurag
"Rick Denoire" <100.17706_at_germanynet.de> wrote in message news:j36t5vcqtc14rrm8spiof4v93vijh0q6sd_at_4ax.com...
> "Anurag Varma" <avdbi_at_hotmail.com> wrote:
>
> >Rick,
> >
> >What do the following queries say:
> >
> >select tablespace_name, contents, extent_management, initial_extent, allocation_type
> >from dba_tablespaces where tablespace_name = '<yourtablespacenamehere>';
>
> From my head: TEMP, locally managed, 4 MB, uniform
>
> >and
> >
> >select name, value from v$parameter where name in ('sort_area_size', 'hash_area_size');
>
> That I will have to query tomorrow at office.
>
> >hash operations also use temp tablespace. However, I have seen this happen primarily in places where
> >the so called temporary tablespace is defined with contents "permanent" i.e. not exactly a temporary tablespace.
> >Happens when hash_area_size is much bigger than the uniform extent size of the temp tablespace.
>
> TEMP is temporary, not permanent. Your hint with hash_area_size means
> that I would need to diminish its value, right?
>
> Thanks
>
> Rick Denoire
Received on Mon Mar 03 2003 - 01:18:55 CST