Re: Index rebuilding behavior

From: Mikel <not_at_me.com>
Date: Tue, 10 Aug 1999 22:37:00 -0400
Message-ID: <Vr5s3.59164$jl.37357835@newscontent-01.sprint.ca>

Rose,

Apart from having the extents for one index in more than one tablespace??? Unless you specify minimum extent XXX, I believe you can get smaller extents than your next and initial default storage clause parameters. However, I don't believe you should get larger extents than you initial and next. Someone much smarter than me will have to tell you exactly how Oracle determines the exact extent size.

Mike

<skubiszewski_at_Eisner.DECUS.Org> wrote in message news:FG216G.9IH_at_news.decus.org...
> In article <7ocl5d$n5v$1_at_nnrp1.deja.com>, Tim_Cuthbertson_at_sonat.com
writes:
> >In article <FFyG1o.DEp_at_news.decus.org>,
> > skubiszewski_at_Eisner.DECUS.Org wrote:
> >> [snip]
> >> How does rebuild work?
> >>
> >> Rose
> >>
> >
> >I am sorry, but I cannot understand what you are describing. An index
> >is a segment, and a segment can only have extents in one tablespace
> >(unless it is a partioned index in Oracle 8 +). Is it a partitioned
> >index?

>

> I'm using Oracle v7.3.4. If I query the extents that comprise the
> index, I see 24 total, in various sizes and tablespaces.

>

> After I issue an "alter index <name> rebuild storage (initial xxx
> next xxx pctincrease 0) tablespace yyy", I see 6 extents, in various
> sizes and tablespaces for the index.

>

> I expected extents of size xxx in tablespace yyy but that's not
> what happened and I'm curious why. Rebuild does not appear to
> honor the storage clause?

>
> Rose
Received on Tue Aug 10 1999 - 21:37:00 CDT