Oracle 版本: 10.2

?

NOLOGGING is supported in only a subset of the locations that support LOGGING . Only the following operations support the NOLOGGING mode:

?

DML : ?

• Direct-path INSERT (serial or parallel) resulting either from an INSERT or a MERGE statement. NOLOGGING is not applicable to any UPDATE operations resulting from the MERGE statement.

• Direct Loader (SQL*Loader)

DDL : ?

• CREATE TABLE ... AS SELECT

• CREATE TABLE ... LOB_storage_clause ... LOB_parameters ... NOCACHE | CACHE READS

• ALTER TABLE ... LOB_storage_clause ... LOB_parameters ... NOCACHE | CACHE READS (to specify logging of newly created LOB columns)

• ALTER TABLE ... modify_LOB_storage_clause ... modify_LOB_parameters ... NOCACHE | CACHE READS (to change logging of existing LOB columns)

• ALTER TABLE ... MOVE

• ALTER TABLE ... (all partition operations that involve data movement)

  • ALTER TABLE ... ADD PARTITION (hash partition only)

  • ALTER TABLE ... MERGE PARTITIONS

  • ALTER TABLE ... SPLIT PARTITION

  • ALTER TABLE ... MOVE PARTITION

  • ALTER TABLE ... MODIFY PARTITION ... ADD SUBPARTITION

  • ALTER TABLE ... MODIFY PARTITION ... COALESCE SUBPARTITION

• CREATE INDEX

• ALTER INDEX ... REBUILD

• ALTER INDEX ... REBUILD [SUB]PARTITION

• ALTER INDEX ... SPLIT PARTITION

For objects other than LOBs , if you omit this clause, then the logging attribute of the object defaults to the logging attribute of the tablespace in which it resides.

------------------------------------------------------

?

Consider Using NOLOGGING When Creating Tables/Index
??? Space is saved in the redo log files.
??? The time it takes to create the index/tables is decreased.
??? Performance improves for parallel creation of large indexes/tables.