Re: Reached limit on Temp Tablespace Extents

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.
|> Any suggestions would be appreciated
|> Guy

The maximum number of segment extents which oracle supports is platform specific. For example on many unix variants the max extents per segment is 121. You should allocate more temp space and temp change your temp tablepsace assignment to build the index. Make the default storage params for initial extent size large so that you do not run out of extents.

Hope this helps.

-- 

Thanks,
-------------------------------------------------------
Joe Minnich                  jminnich_at_bugaboo.ssnet.com
System Administrator         302-791-8662
Electronic Payment Services