Re: Extent sizes in LMT

From: andrew_webby at hotmail <spam_at_no.thanks.com>
Date: Mon, 4 Jun 2001 17:28:31 +0100
Message-ID: <991672126.7995.0.nnrp-10.c30bdde2@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 - 11:28:31 CDT