Re: Reached limit on Temp Tablespace Extents

From: Chaz Sliger <chaz_at_atlas.com>
Date: Tue, 18 Oct 1994 00:24:26 GMT
Message-ID: <1994Oct18.002426.14104_at_atlas.com>


In article <1994Oct5.230842.1_at_gmuvax.gmu.edu> bgilst_at_gmuvax.gmu.edu writes:
>Hi,
> My TEMP table space cannot extend any futher when I am trying to build an
>index. The first time it was at 99 extents, so I raised it to 500(I think the
>actual limit is 256). Now it stops at 122. I don't understand this. If
>nothing is permanently stored in the temporary tablespace, why doesn't it use
>all the space. The temporary tablespace is 5M and my data and index tablespaces
>are 10M each, so I feel I should have plenty of space. Can I defragment the
>temporary tablespace somehow to get rid of the extents(I couldn't find this in
>any book. Oracle error book says to add another datafile, Great). Can I just
>drop the TEMP tablespace and recreate it? Also, I am using Oracle Version 6,
>VMS, and no one else is running an Oracle transaction while I'm trying to build
>this index.

	The limit on extents is 122.
	It's a good idea to set the max to 120 so you have a couple
	left over when it hits the wall.
	You can then increase the max and allocate a large extent
	to keep the system going until you can schedule some time
	to rebuild.

-- 

	==========================================================
	Chaz Sliger     |     -\     "Let the rough side drag,
	Portland, OR    --\_(HD)\     Let the smooth side show..."
Received on Tue Oct 18 1994 - 01:24:26 CET

Original text of this message