RE: Log file sync and log file parallel write.

  • From: "Johnson, William L (TEIS)" <WLJohnson@xxxxxxxxxxxxxxxxxxx>
  • To: "Jared Still" <jkstill@xxxxxxxxx>, <asif_oracle@xxxxxxxxx>
  • Date: Wed, 5 Mar 2008 20:37:45 -0500

Can someone help point me to documentation that will show me the silver
bullet for not rebuilding indexes?  I can provide countless examples
over the past several years where rebuilding indexes corrected
performance problems that developed over months.  Are we saying that
something else fixed the problem and that the index rebuild was not the
real solution?  Is the index rebuild forcing explain plans out of the
shared_pool and giving false results?  If so, wouldn't a DB stop/start
accomplish the same result?  I am by no means an optimizing expert, but
won't Oracle switch to something like full table scans if the index is
no longer an effective method to obtain your data?  This quickly becomes
a problem when joining multiple tables with 10+ million rows each.   I
deal a lot with third party applications like SAP, Click Commerce and
Matrix One Engineering modules where we can not alter the sql running
behind the scenes.

 

I would really like to understand.

 

Bill

 

________________________________

From: Jared Still [mailto:jkstill@xxxxxxxxx] 
Sent: Wednesday, March 05, 2008 7:39 PM
To: asif_oracle@xxxxxxxxx
Cc: Johnson, William L (TEIS); oracle-l@xxxxxxxxxxxxx
Subject: Re: Log file sync and log file parallel write.

 

        
        Lastly, why are you rebuilding your indexes???
        Regards
        Asif Momen
        http://momendba.blogspot.com

         



Same question. Why are you rebuilding the indexes?

You *could* just stop doing that.

-- 
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist

Other related posts: