Re: Do LMT's ignore initial & next parameters in the storage clause?

From: Richard Foote <richard.foote_at_bigpond.nospam.com>
Date: Sun, 29 Oct 2006 13:18:13 GMT
Message-ID: <pS11h.55311$rP1.43453@news-server.bigpond.net.au>

"Ben" <balvey_at_comcast.net> wrote in message news:1161980598.117535.230600_at_i42g2000cwa.googlegroups.com...
> 9.2.0.5 Ent Ed.
> I create a locally managed tablespace with uniform/manual extent
> allocation set to 1M. Then I create an index or table in that LMT but
> include a storage clause with initial set to 20M and next set to 1M.
> Are these parameters ignored and instead the object has 1M extent
> sizes? I believe I already know the answer, as I have done this and it
> looks as though this is true, but I didn't understand why it would let
> you set those values in the storage clause and then ignore them.
>

Hi Ben

The storage parameters are not totally ignored, they're still used to determine the initial size of the object, however this initial allocation of storage is allocated in x number of uniform sized extents.

So in your example above, instead of having 1 x 20m extent, Oracle will allocate 20 x 1M extents. Note next, minextents and pctincrease if specified are also used to determine the initial storage allocation.

It lets you set those values not only for the above but also for backward compatibility reasons.

Cheers

Richard Received on Sun Oct 29 2006 - 07:18:13 CST