Re: contiguous space??

A next extent size of 250 M is pretty large. Yes it is looking for 250 M of contigous space. There are tools like DB Reorg that will defrag for you.

The storage parameters at the tablespace level are specified and applied to tables that do not have their own storage clause. A default if you will. But you have specified at the table level, so those over-ride.

--
John Jones
Senior Oracle DBA
Duke University, OIT
john.jones_at_duke.edu
<gdas_at_my-deja.com> wrote in message news:91o7uh$7bh$1_at_nnrp1.deja.com...


> 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/