RE: Temp. segments/extents not being dropped

This is my understanding of how the process is SUPPOSED to work too!

But what I am experiencing is different.

Extents are staying allocated and unusable by other users/transactions.

Thanks for your reply.

"Gopal , Umesh" <ugopal_at_proxicom.com>@fatcity.com on 06/05/2000 04:01:16 PM

Please respond to ORACLE-L_at_fatcity.com

Sent by: root_at_fatcity.com

Sent From the mail file of: Dan Hubler

To: Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com> cc:

Subject: RE: Temp. segments/extents not being dropped

If the temporary tablespace is defined as temporary SMON would not deallocate the storage space allocated to temporary segements unless forced as u did or when the instance is brought down. If the temporary tablespace is not defined as temporary then smon will clearup the temporary segments that were created after the completion or failure of the sql statement

this is what I have gathered from one of the OCP questions that I came across,

all out there, correct me if I am wrong

-----Original Message-----
Sent: Monday, June 05, 2000 3:03 PM
To: Multiple recipients of list ORACLE-L

Looking for some information on the following:

We had an incident last week where an Oracle instance (7.3.4.4) on NT was running into problems acquiring space for additional extents on the defined temporary tablespace.

While looking at the situation, we discovered that there was just about zero
free space left in the tablespace. There was a whole bunch of extents created and owned by "SYS" and they had some flaky numeric identifier for the segment-name (something like 37.123).

Other processes were failing, being unable to allocate temp space.

We looked around on Metalink, and discovered a note about forcing temporary segments/extents to be cleaned up by performing an "ALTER TABLESPACE TEMP DEFAULT STORAGE (PCTINCREASE 0);"

We executed the statement. Lo and behold, all the segments disappeared, back into
free space.

My guess is that there was a large sort (we do some of those) that failed, and left segments out there. I do not understand why they wouldn't clean up.

Any information?

--
Author:
  INET: Dan.Hubler_at_midata.com

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: ListGuru_at_fatcity.com (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).
--
Author: Gopal , Umesh
  INET: ugopal_at_proxicom.com

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: ListGuru_at_fatcity.com (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