There is much to be read about the need or otherwise to rebuild indexes - infact at the moment it's hard to avoid it! My interpretation of what I read is that it is rarely necessary/useful. (And can wreck your indexes - been there, done that, very colourful T-shirt). So you'd better know what you're doing and why.
The nologging is the "best" you can do in an index rebuild.
Use the logging_clause to specify whether subsequent Direct Loader (SQL*Loader) and direct-path INSERT operations against a nonpartitioned index, a range or hash index partition, or all partitions or subpartitions of a composite-partitioned index will be logged (LOGGING) or not logged (NOLOGGING) in the redo log file.
P.S. AFAIK direct-path, direct load refer to operations on the table, not the index.
Last edited by DaPi; 04-19-2005 at 03:45 PM.
"The power of instruction is seldom of much efficacy except in those happy dispositions where it is almost superfluous" - Gibbon, quoted by R.P.Feynman