Re: Temp tablespace Initial extent question

> I'm wondering what is the penalty of having an initial extent in a
> temp tablespace that is set too large? We have an app that connects

The only one that comes to mind is that you might end up with failing queries if the next concurrent user needs a temp segment & all the space in the tablespace is already allocated to other transactions because the initial size is big regardless of actual need.

> to oracle as a single username. The application performs queries
> against small tables as well as against very large tables (2+ million
> rows). Performance is slow against the large tables due to the order
> by clause in the queries (which are needed). When I analyze the
> performance of these queries, I'm finding that oracle is spending 99%
> of it's time, just sorting the data.

I doubt that the initial extent size has anything to do with it -- the query may need to be optimized to reduce the amount of sorting needed or you can try playing with sort_area_size to reduce disk I/O Received on Mon Dec 03 2001 - 14:31:58 CST