On July 5, 2001 07:55 pm, [EMAIL PROTECTED] wrote:
> Hi,
> One of the generic users (multiple people use the same
> logon/password) on one of my db's has been assigned temporary
> tablespace which is a permanent tablespace type, i.e.
> (select contents from dba_tablespaces where
> tablespace_name=my_ts_name; returns PERMANENT).
> I was told by let it stay that way. I am investigating the whole
> thing (just for myself). Is there any true reason why the user
> would need their temp tablespace to be permanent? Could my
> situation cause any major problems? If so, what things I need keep
> my eye on in order to avoid them? Thank you.
> Lyuda Hoska
No reason why a temporary tablespace should be permanent. Using a
temporary temp tablespace is more for performance and ease of
management - you can create temporary objects in a permanent
tablespace, however the extents will be allocated and deallocated as
needed (leading to fragentation of the free space if you are not
following a uniform extent policy for objects). However, with a
temporary temp tablespace, the extents are allocated and left
allocated, allow future temporary objects to use the
already-allocated extents. Plus, in a true temporary tablespace,
permanent objects cannot be created, easing your admin/maintenance
time.
HTH,
GC
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Gregory Conron
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
