This discussion is archived
1 3 4 5 6 7 Previous Next 92 Replies Latest reply: Nov 27, 2009 12:11 AM by Hemant K Chitale Go to original post RSS
  • 90. Re: corrupted indexes
    635471 Expert
    Currently Being Moderated
    burleson wrote:
    It sounds like Hemant has been crippled by bitmap freelists (ASSM), a feature that was never intended for high-volume production databases:

    Slow for full-table scans — Several studies have shown that large-table full-table scans (FTS) will run longer with ASSM than standard bitmaps. ASSM-FTS tablespaces are consistently slower than Freelist-FTS operations. This implies that ASSM may not be appropriate for decision support systems and warehouse applications, unless partitioning is used with Oracle Parallel Query.
    Do you have a reference for these studies?
  • 91. Re: corrupted indexes
    userxyz1234 Explorer
    Currently Being Moderated
  • 92. Re: corrupted indexes
    Hemant K Chitale Oracle ACE
    Currently Being Moderated
    UPDATE BY HEMANT K CHITALE (the same person !)

    I understand that Burleson has quoted this posting of mine, quite out of context at in his article on [Online Index Rebuilding.|]

    NOTE : I do not recommend rebuilding of ALL indexes weekly. This was a specific table (and I have identified only three such likely tables in a database of thousands of tables) that may require : Preferably a COALECE (as adviced by Jonathan Lewis) -- if I can get the code changed !! -- or, as the second best option, a regular REBUILD.

    The behaviour described in Oracle Bug#6447841 matches what I have seen. This is [clear later in this same thread|]

    Here are two postings on my blog where I discuss Rebuilding Indexes -- in general, not relating to the behaviour described in Bug 6447841.

    [1. Rebuilding Indexes|]
    [2. Rebuilding Indexes - When and Why ?|]

    Hemant K Chitale
1 3 4 5 6 7 Previous Next


  • Correct Answers - 10 points
  • Helpful Answers - 5 points