Re: Oversized TEMP space

As it happens, somebody has submitted to me today a query that runs out of temp space (after running, as you can guess, for quite a while). As usual, rejuggling the query solved the problem. I have seen queries running out of tens of gigabytes of temp space. If you can drill the issue down to a single query, playing with it may not be a waste of time IMHO. What I dislike with the 'increase xxx' approach is that you never know by how much, nor how long it will shield you from a new occurrence of the problem.

SF

Barr, Stephen wrote:

> Are there any possible issues with oversizing a TEMP tablespace?
>
>
>
> Would it affect any of the costing algorithms?
>
>
>
> Are there any other downsides other than the small management overhead?
>
> ------------------------------------------------------------------------

--
http://www.freelists.org/webpage/oracle-l