Re: faulty system index creation algorithm?

Since you did not set the storage parameters for the indexes these indexes were created with default storage parameters. There is no Magic Storage Algorithm For Primary Keys(MSAFPK), although it sounds like a great Idea to for Oracle to use a default for a primary key based on the amount of space allocated to the table. As for dropping and recreating them you could do that by dropping the constraint or just use the ALTER INDEX indexname REBUILD STORAGE (INITIAL 100K NEXT 50K) TABLESPACE indextablespacename;

Doug wrote:

> I was recently analyzing some tables to check if they have been
> growing as projected several months ago, and discovered that the
> only objects who had exceeded the initial extent that I had provided
> for them were the indexes on the primary key values. These indexes I
> would guess are sized and estimated by Oracle itself and
> probably based on the datatype chosen for the primary key. I cannot
> drop and re-create these indexes, so my question is this - Does Oracle
> size primary key indexes incorrectly? In one case I
> had 25 extents after I consider to be very minimal table growth. This
> is not a serious problem in anyone's view at my site, these tables are
> in fact very small - the entire set in the schema is less than 1MB -
> but I was surprised. Any thoughts?
>
> Just curious -
>
> Thanks,
> Dc.
Received on Sun May 17 1998 - 07:09:33 CDT