CREATE INDEX vs. ALTER INDEX REBUILD

Can anybody point me to some documentation about what goes on during a CREATE INDEX and a ALTER INDEX REBUILD? I am trying to figure out if ALTER INDEX REBUILD reads the old index to create the "rebuilt" index, or if the REBUILD goes back to the table to create the "rebuilt" index. I have an idea, but I need definitive proof.

For example, if I have a table (XYZ) that has 1 million rows and an index (XYZ_PK) that is a unique index on that table. If I issue CREATE UNIQUE INDEX xyz_pk ON xyz(x) of course every row in XYZ will be read. However, if I issue ALTER INDEX xyz_pk REBUILD, does Oracle read XYZ_PK and re-organize the blocks or does it read XYZ to build the new index?

Use the ALTER INDEX ... REBUILD statement to reorganize or compact an existing index or to change its storage characteristics. The REBUILD statement uses the existing index as the basis for the new one. All index storage statements are supported, such as STORAGE (for extent allocation), TABLESPACE (to move the index to a new tablespace), and INITRANS (to change the initial number of entries).

ALTER INDEX ... REBUILD is usually faster than dropping and re-creating an index, because this statement uses the fast full scan feature. It reads all the index blocks using multiblock I/O then discards the branch blocks. A further advantage of this approach is that the old index is still available for queries while the rebuild is in progress.

http://download-west.oracle.com/docs..._acce.htm#7531


Does that help?

MH

That would be it! I've been looking at the Concepts and Admin guide for over an hour...

When rebuilding a normal index, the statistics for that index are not affected.

SQL> create index x_test on test ( y ) global;

Index created.

SQL> analyze table test compute statistics;

Table analyzed.

SQL> select index_name, leaf_blocks from user_indexes;

INDEX_NAME LEAF_BLOCKS
------------------------------ -----------
X_TEST 3

SQL> alter index X_TEST rebuild;

Index altered.

SQL> select index_name, leaf_blocks from user_indexes;

INDEX_NAME LEAF_BLOCKS
------------------------------ -----------
X_TEST 3

Thus no change to the statistics when the index has been rebuilt.

Well, in that case.......ahem...

IT TOOK ME 30 SECONDS TO FIND THIS ON TAHITI, I SUGGEST YOU DO A LITTLE HOMEWORK BEFORE POSTING HERE!!


C'mon, I've been waiting to say that for at least 2 years. ;)

Who do you love?

MH

Quote:

---

Originally posted by Mr.Hanky
C'mon, I've been waiting to say that for at least 2 years. ;)

---

U got patience man...
2 years of waiting to be able to say those words... :D

Quote:

---

Originally posted by adewri
U got patience man...
2 years of waiting to be able to say those words... :D

---

U do as well to reply......:)

n ofcourse myself to point u.......;)

Quote:

---

Originally posted by arjun
When rebuilding a normal index, the statistics for that index are not affected.

SQL> create index x_test on test ( y ) global;

Index created.

SQL> analyze table test compute statistics;

Table analyzed.

SQL> select index_name, leaf_blocks from user_indexes;

INDEX_NAME LEAF_BLOCKS
------------------------------ -----------
X_TEST 3

SQL> alter index X_TEST rebuild;

Index altered.

SQL> select index_name, leaf_blocks from user_indexes;

INDEX_NAME LEAF_BLOCKS
------------------------------ -----------
X_TEST 3

Thus no change to the statistics when the index has been rebuilt.

---

When you rebuild them then you must know why you're rebuilding them.
You want them to stay "compact" as you planned or make them airy so the levels don't increase that fast...and then add pctfree in that clause............