Search notes:

Oracle: redo data

Redo records all changes that are made to a database (even UNDO) in a stream of redo records. These recorded changes are needed to recover a database.

LOGGING and NOLOGGING

Certain operations that change data can be executed with LOGGING or NOLOGGING. If performed with NOLOGGING, no redo data will be generated.
The operations where the logging clause can be applied are the create and alter SQL statements for the following objects:
Two special statements where it can applied are also
NOLOGGING can also be used in direct path inserts and SQL*Loader.
The NOLOGGING clause is ignored if the respective object is located in a database or tablespace with force logging.
Operations on objects in a temp file are always executed with NOLOGGING.

See also

redo record
commit
undo data
The /*+ append */ hint
The redo size statistics.
The amount of redo generated for update statements can be reduced by using dbms_redefinition.execute_update.

Index