Use Nologging tom improve the loading performance

Nologging is designed to handle bulk inserts of data which is reproducable.
Nologging has no effect on update, delete and insert statements.
Nologging can be applied on table or table space

(For Oracle 11g, use APPEND_VALUES instead of APPEND hint to bypass the redo log)

Nologging is active when performing one of the following commands:

direct load (SQL*Loader)
direct load INSERT (using APPEND hint)
CREATE TABLE … AS SELECT
CREATE INDEX
ALTER TABLE MOVE
ALTER TABLE … MOVE PARTITION
ALTER TABLE … SPLIT PARTITION
ALTER TABLE MERGE PARTITION
ALTER TABLE MODIFY PARTITION ADD SUBPARTITON
ALTER TABLE MODIFY PARTITION COALESCE SUBPARTITON
ALTER INDEX … SPLIT PARTITION
ALTER INDEX … REBUILD
ALTER INDEX … REBUILD PARTITION

The test on OIS shows that nologging has no meaning on the runtime:
--nolog1,23-AUG-13 02.27.45.000000000 PM to 23-AUG-13 02.53.10.000000000 PM
--nolog2,23-AUG-13 02.57.04.000000000 PM to 23-AUG-13 03.22.14.000000000 PM
--log,   23-AUG-13 03.31.00.000000000 PM to 23-AUG-13 03.51.56.000000000 PM