Re: When to rebuild the index?

Sure.. I thouht I miss to configure something.
 Let me do this and if I will come across something like this, I will be 
more than happy to share with you guys.
 Thank you,
 Regards - Chirag 

 On 9/6/05, Allen, Brandon <Brandon.Allen@xxxxxxxxxxx> wrote: 
> 
> I know - it's kind of a pain. Search Metalink for index_stats and you 
> should find a script that you can run which will create a stored procedure 
> and generate a secondary script to run validate structure on each index and 
> then insert the values from index_stats into a secondary table, e.g. 
> all_index_stats.
> 
> -----Original Message-----
> *From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto:
> oracle-l-bounce@xxxxxxxxxxxxx]*On Behalf Of *Chirag DBA
> *Sent:* Tuesday, September 06, 2005 10:07 AM
> *To:* Chirag DBA
> *Cc:* Oracle-L Freelists
> *Subject:* Re: When to rebuild the index?
> 
> While you do the validate structure with indexes, it shows the stats only 
> for the last index.
>  How can I see the list of all the indexes who needs to get rebuild now.
>  I can see the results only for 1 index and that is the last one in 
> valudate structure.
>  Regards - Chirag 
> 
>  On 9/6/05, Chirag DBA <chiragdba@xxxxxxxxx> wrote: 
> > 
> > Hi Guys,
> >  I think that even select statement will make the index split and 
> > require the rebuilding. Am I true? I think I am.
> >  And there is a view called index_stats with column height. 
> >  I have read that when the value of this column is >= 4, u need to 
> > rebuild the indexes.
> > But after analyzing the particular schema, I don see any value to get 
> > populated in this view.
> >  I can see last analyzed value changed in dba_indexes when I analyze the 
> > schema with DBMS_STATS. ANALYZE_SCHEMA package.
> >  Why this is so? 
> >  Regards - Chirag 
> >  
> 
>  Privileged/Confidential Information may be contained in this message or 
> attachments hereto. Please advise immediately if you or your employer do not 
> consent to Internet email for messages of this kind. Opinions, conclusions 
> and other information in this message that do not relate to the official 
> business of this company shall be understood as neither given nor endorsed 
> by it.
>

Other related posts: