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

Ben wrote:
> 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.

The uniform extent size that you specified on the tablespace will over-ride any initial or next specifications for indexes or tables created or moved into the tablespace. This is very helpful for those packaged applications that use 30 different storage clauses that do nothing but cause fragmentation in the tablespace. Problems are fixed automatically when an import is performed, or the table or index is moved to the tablespace.

Charles Hooper
PC Support Specialist
K&M Machine-Fabricating, Inc. Received on Fri Oct 27 2006 - 17:21:09 CDT