After validating the index you can check its space stats, and can calculate space used by per row. than by using some maths u can get the IDEA of the space that u'll gain after rebuilding.
This poses the question "WHY?", if the index is fragmented, re-build it. You can view the space gains in OEM by looking at the space used for that tablespace before and after.
Are you re-building to regain space or to correct fragmentation?
About estimate size of index extent after rebulid:
In first: u have to know type of indexes
-- compressed or not compressed
-- b+ or bit map
In second: (and this is more interesting thing) u have to know
HOW ROWS WITH SOME INDEX KEY VALUES DISTRIBUTED IN REAL TABLE.
Why:
index segment (not compressed) can keep 2 kind of entry:
1) key value + rowid
2) key value + (rowid_start, rowid_end)
In this case we have (NOTE with the same # of rows in 1 table block)
Bookmarks