After wrting a short series of notes on a problem with indexes wasting a lot of space and growing to three (or even four) times the size you might expect due to a problem with concurrency and ITL (interested transaction list) entries accumulating, I thought it would be a good idea to create a little index for the series to make it easier to read them in order:
- Index Quiz 1 : An introductory question
- Index Quiz 2 : Answering the question with block dumps
- Index Explosion : Demonstrating the issue
- Index Explosion – 2 : Explaining the problem
- Index Explosion – 3 : Solving the problem
- Index Explosion – 4 : Working around the problem
- Index ITL fix: Announcing the patch (which is a bit of a compromise)
- treedump : A useful (though sometimes expensive) option for looking into index structures
- treedump 2: Another look at tree dumps.
Oracle Scratchpad 
[…] handle leaf node splits that can appear even at fairly low levels of concurrency . This results in excess ITL entries being allocated in the new leaf nodes. Once the ITL entires have been allocated they are always propagated across […]
Pingback by Index Efficiency 3 « Oracle Scratchpad — March 3, 2010 @ 9:21 pm GMT Mar 3,2010 |
[…] transaction list), how and when they become huge and make index bigger in size – see this post with links to several other articles. As it turned out in a recent thread on SQL.ru forum, one of […]
Pingback by Index ITL « Timur Akhmadeev's blog — April 27, 2010 @ 7:57 pm BST Apr 27,2010 |
[…] have written several notes about a problem with leaf block splits that used to appear occasionally in systems that used […]
Pingback by Fragmentation 4 « Oracle Scratchpad — July 22, 2010 @ 7:02 pm BST Jul 22,2010 |