Re: contiguous space??

Yes, the problem is probably caused by lack of contiguous space in the tablespace. Query the dba_free_space view to get a list of the available extents in the tablespace. If the largest extent is smaller than the extent being requested, then the opbject can not extend.

Your message indicates that the 'tablespace' couldn't extend. Do you have autoextend set on? If that is truly the case, then the drive where the datafiles for the tablespace are located could be full.

The answer to your last question is that the maxextents specified at the tablespace level will only be used if an object is created in that tablespace and a maxextent value is not specified in the create statement.

Hope this helps.
Patrick ....

In article <91o7uh$7bh$1_at_nnrp1.deja.com>,   gdas_at_my-deja.com wrote:
> Today, our app reported that a tablespace could not be extended...
>
> The tablespace has almost 1 Gig free (according to dba_free_space).
> And the next_extent for the object it was trying to extend which
> reported the error (in this case an index) was 250 MB. The maxentents
> had not yet been reached on the object.
>
> So, I'm wondering if this problem is being caused due to a lack of
> contiguos space on the Hard Drive? Or could it be because of
 something
> else. If it is due to lack of contiguous space, is there anyway to
> unfragment things (aside from recreating and reimporting the
 database)?
> I've tried coalescing the tablespaces and that didn't seem to help.
>
> Also, an aside question perhaps related... If the maxextents on a
> tablespace is 121 yet the maxextents on an object in that tablespace
 is
> 256, does that present a problem? Do the storage properties of a
> tablespace have any meaning other than simply being default values for
> the objects in that tablespace?
>
> Thanks for any advice.
> Gavin
>
> Sent via Deja.com
> http://www.deja.com/
>

Sent via Deja.com
http://www.deja.com/ Received on Tue Dec 19 2000 - 14:00:56 CST