Re: Lost Table Space

Yes.

Oracle requires that there be sufficient contiguous disk space to hold an extent.

If all of the extents in the tablespace are the same size you do not have to ever defrag and all of the space assigned to the tablespace will be available for use. The trade off is disk space vs. ease of maintenance. If you define tablespaces with DEFAULT STORAGE clause values where INITIAL and NEXT are the same size and PCTINCREASE is 0 and do not include STORAGE clauses in your other CREATE statements (and never import a table that was exported with COMPRESS=Y) you will never have to coalesce, export then import, or do anything else related to defragging a tablespace.

If the objects in a tablespace have differing extent sizes and some of the smaller items have been deleted the result is a substantial amount of free space organized in chunks too small to hold an extent for one or the larger objects.

hth
jerry gitomer

KM wrote in message <7uo898$ja1$1_at_bgtnsc02.worldnet.att.net>...
>Is it the case that the space set for the "initial" parameter
must be
>contigaous? That is, the table space may have 4 GB of
fragmented space
>available, but not a contigaous chunk of 1GB for the new table?
>
>What is the recommended way to defrag table space of such size
(10 GB
>allocated)?
>
>Thanks again!
>

    [snip]

>
Received on Fri Oct 22 1999 - 11:57:24 CDT