Re: Extent sizes in LMT

It's in it's own tablespace but the problem here is that I need to be informed when the table is going to fail to extend days in advance. Our scripts to report on this runs daily. The extents are so small that I get no notification. (i.e. it's extending more than once a day).

"andrew_webby at hotmail" <spam_at_no.thanks.com> wrote in message news:991672126.7995.0.nnrp-10.c30bdde2_at_news.demon.co.uk...
> No way to specify a different next from initial - as the term suggest,
> they're uniformly sized.
>
> You could perhaps move the table to another tablespace with more
> appropriately sized extents? If this table is in its own tablespace, then
> the number of extents shouldn't be a worry (and that worry tends to
> disappear with LMTs anyway, doesn't it?).
>
> "Chuck Hamilton" <chuck_hamilton_at_hotmail.com> wrote in message
> news:9fgc8d$3r188$1_at_ID-85580.news.dfncis.de...
> > In a locally managed tablespace with uniformly sized extents, is there
 any
> > way to specify a next extent size for objects in the tablesapce?
> >
> > Why would I want to do this? I have a nightly script that reports on
 objects
> > that will fail to allocate their next extent. I want the extents to be
 large
> > enough so that I get a week of advance warning before failure occurs.
 One
> > table's growth rate was severly underestimated and now I'm stuck with
 10m
> > extents on a 10g table that's growing at 11m per day. The table is
 receiving
> > inserts 24x7 and needs to be available continuously. Any suggestions
 would
> > be appreciated.
> > --
> > If at first you don't succeed, skydiving isn't for you!
> >
> > Chuck Hamilton
> > chuck_hamilton_at_hotmail.com
> >
> >
> >
>
>
Received on Mon Jun 04 2001 - 12:59:42 CDT