Re: Changing the status of temporary tablespace to permanent

Short sharp answer: nothing will happen. Queries that rely on sort runs being swapped out to temporary tablespace will take longer (because extent allocation and de-allocation has to take place in permanent tablespace. In temporary tablespace, extents are simply re-used by new queries once old queries have finished). The quantity of redo generated will go up (and hence provide further reasons for performance degradation). You may get idiot junior DBAs creating real tables or indexes (or other 'permanent objects') in the tablespace, chewing up space.

But other than that, the database will not blow up, and the sky won't fall in. That said, it's not something you want to be doing just for the hell of it.

Regards
HJR

--
=============================!!=============================
The views expressed are my own only, and definitely NOT those of Oracle
Corporation
=============================!!=============================


"Dark Lord" <darklord29_at_mailandnews.com> wrote in message
news:_5ER6.18644$zl5.4980633_at_typhoon.ne.mediaone.net...


> Hi,

>   Quick basic question, if such a thing exists :) Suppose I change the

> status of my temporary tablespace ( temp) to permanent. What are the

 likely


> results of my action ? Thanks

>

> --

> Silent Running