Re: temporary tablespaces

On 12 Sep 2003 18:34:02 GMT, Chuck <chuckh_at_softhome.net> wrote:

>"Sybrand Bakker" <postbus_at_sybrandb.nospam.demon.nl> wrote in
>news:vm3vv8duaeofeb_at_corp.supernews.com:
>
>>
>> "David COSTE" <dco_at_compaq.com> wrote in message
>> news:Onl8b.4630$je2.2848_at_news.cpqcorp.net...
>>> It's because my batch processing consumes temporary segments and I
>>> don't want to see it run out of space because some one would have
>>> launched a big query with an order by.
>>> The idea is to avoid sharing the same temp tablespace for the 2
>> activities.
>>>
>>>
>> This is not going to help you at all. If you set up 2 different
>> tablespaces for 2 different users/processes, those processes will
>> still be capable to have your temp tablespaces out of space.
>> Make sure you have adequate space, as disk is cheap, and stop symptom
>> fighting.
>>
>>
>
>Huh? If two users are using two completely different temporary
>tablespaces, how does one cause the other to run out of space? Of course
>I assuming that you do *NOT* have autoextend enabled on the tempfiles.

You are misunderstanding me. Even if every individual user would have it's own temporary tablespace, he still would be capable to run out of space in that individual tablespace. Autoextend doesn't come into play, because the way he is approaching it, he would be also afraid to run out of disk space.
The OP is accomplishing nothing, except *believing* he is reducing risks. One adequately configured temporary tablespace will do. He doesn't seem to want to take that route though, but rather fight symptoms by setting up more tablespaces.

Sybrand Bakker, Senior Oracle DBA

To reply remove -verwijderdit from my e-mail address Received on Sat Sep 13 2003 - 00:17:53 CDT