That is what Oracle DBA's say, and it also disagrees with what Oracle says.
Have a look at the last document on this page:
http://otn.oracle.com/deploy/performance/listing.htm
--
Syltrem
http://pages.infinit.net/syltrem (OpenVMS Web Site)
"Daniel A. Morgan" <dmorgan_at_exesolutions.com> wrote in message
news:3A6FBBA2.4F17BAF2_at_exesolutions.com...
> > I am trying (hard!) to get same size extents throughout my tablespace,
but
> > Oracle *8.0.5.1) won't let me do it.
> >
> > NEXT_EXTENT keeps changing for about 20 tables (out of 1500). Please
someone
> > have a look at the following sequence and tell me what I do wrong or do
not
> > understand!
> > Note: I picked a bad example maybe (numbers are look alike)
> > I want extent size = 160 (one-sixty) and Oracle changes for 168
> > (one-sixty-eight)
> > a) table created with extent=160k
> > b) import data
> > c) extent now 168
> > d) truncate table
> > e) extent back to 160
> >
>
> I can not imagine why it is happening unless you have pctincrease set to a
> non-zero value.. But I can not imagine why you would want the EXTENT sizes
to be
> the same. That is pretty much the definition of a bad design.
>
> Reasonable people will disagree on this but for myself, initial extents
should
> be sized to hold, as near as possible, 1 to 3 years worth of data
depending on
> the application. Next extents are generally sized, again depending upon
> anticipated table growth, at between 25% and 100% of initial extent size.
And
> please please set PCTINCREASE to ZERO for all tables and indexes.
>
> Daniel A. Morgan
>
Received on Thu Jan 25 2001 - 08:29:00 CST
