Originally posted by davey23uk will be used for sorting, wont store all of it, but your tablespace will need to be big enough to hold the old and current index
I'd guess that it would depend on whether the index is already usable or unusable -- I don't think that temp space is involved in rebuilding a usable index.
Originally posted by slimdave
I'd guess that it would depend on whether the index is already usable or unusable -- I don't think that temp space is involved in rebuilding a usable index.
Well, still oracle uses temp ts for sorting.
Abhay.
funky...
"I Dont Want To Follow A Path, I would Rather Go Where There Is No Path And Leave A Trail."
"Ego is the worst thing many have, try to overcome it & you will be the best, if not good, person on this earth"
Originally posted by OracleDoc A 30 gig index???!!! Dude that's insane! Ever heard of partitioning?
What if a unique index ( global nonpartitioned index ) is neccesaary for that partitioned table and that key/s is/are not a part of column/s on which table is partitioned?
Abhay.
funky...
"I Dont Want To Follow A Path, I would Rather Go Where There Is No Path And Leave A Trail."
"Ego is the worst thing many have, try to overcome it & you will be the best, if not good, person on this earth"
Slim's point is that if the index is usable, the rebuild is based on the index, NOT the table. The required data can be read in order by reading the chain of leaf blocks, so no sorting should be required.
Slim's point is that if the index is usable, the rebuild is based on the index, NOT the table. The required data can be read in order by reading the chain of leaf blocks, so no sorting should be required.
Well i do understand that point and was of that impression too, but you can check the usage of Temp TS while even rebuilding usable index.
Abhay.
funky...
"I Dont Want To Follow A Path, I would Rather Go Where There Is No Path And Leave A Trail."
"Ego is the worst thing many have, try to overcome it & you will be the best, if not good, person on this earth"
Bookmarks