Effect of nologging and unrecoverable

When no logging operations are executed at the source database by using the nologging or unrecoverable keyword for a SQL operation, the changes resulting from the SQL operation cannot be captured by a Capture process. This is because the nologging operations do not create REDO entries.

Note: If the object for which the logging attributes are specified resides in a database or tablespace in FORCE LOGGING mode, Oracle ignores any nologging or unrecoverable setting until the database or tablespace is taken out of FORCE LOGGING mode.

If the unrecoverable clause is used in the SQL*Loader operation for a direct path load, the table changes resulting from the direct path load cannot be captured by a Capture process. Specifying the unrecoverable clause in the Control File is one example, as noted below.

UNRECOVERABLE
LOAD DATA
INFILE 'myfile.dat'
INTO TABLE salesperson
(sname VARCHAR2(40), salesid NUMBER(4))