Home > 11g >

January 11, 2014

NOLOGGING:

NOLOGGING and be used to prevent bulk operations from logging too much information to Oracle’s Redo log files. Following operations will make use of NOLOGGING option.

SQL*Loader in direct mode
INSERT /*+APPEND*/ …
CTAS
ALTER TABLE statements (move/add/split/merge partitions)
CREATE INDEX
ALTER INDEX statements (move/add/split/merge partitions)

FORCE LOGGING:

On the other hand, FORCE LOGGING can be used on tablespace or database level to force logging of changes to the redo. This may be required for sites that are mining log data, using Oracle Streams or using Data Guard (standby databases).

A tablespace or the entire database is either in force logging or no force logging mode. To see which it is, run:

SELECT force_logging FROM v$database;

To enable force logging:

SQL> ALTER DATABASE force logging;

To disable:

SQL> ALTER DATABASE no force logging;
Database altered.

Advertisements
Categories: 11g
%d bloggers like this: