NOLOGGING attribute tells Oracle that the operation being performed does not need to be recoverable in the event of a failure. In this case, the database will generate only a small set of metadata that is written to the redo log, and the operation will probably run faster. Oracle is relying on the user to recover the data manually in the event of any failure. In other words, the
NOLOGGING option skips the generation of redo for the affected object, but will still log many things such as data dictionary changes caused by space management.
At the tablespace level, the
LOGGING clause specifies the default
LOGGING attribute for all tables, indexes, and partitions created in the tablespace ...