Re: Extent sizes in LMT

It sounds to me as if you really need to do two things with that table - In the short term, move it to a tablespace with a larger uniform extent size. In the longer (short) term, figure out how to partition it.

How about a dbms_job that runs every
night to 'allocate extents' and tries to keep 100MB of free space above the
HWM ? A couple of nights after the
job failed because the tablespace was
full, your report would kick in and report the problem.

--
Jonathan Lewis
Yet another Oracle-related web site:  http://www.jlcomp.demon.co.uk

Practical Oracle 8i:  Building Efficient Databases
Publishers:  Addison-Wesley

Reviews at: http://www.jlcomp.demon.co.uk/book_rev.html



Chuck Hamilton wrote in message <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

>

>

>