Originally posted by pando
you mean that if you create an index with nologging then susquent insert shouldnt generate redo with that index...?
No. Subsequent direct-load insert shouldn't.

If I create an index with nologging clause on populated table, then redo is small.
If I create an index with nologging clause on empty table and then populate the table with direct-load insert, then redo is big.