Oracle Database - Table Logging Mode (LOGGING, NOLOGGING)

Card Puncher Data Processing

About

The logging mode of the target table (LOGGING, NOLOGGING) is what will dictate whether redo log is generated for the table or not.

LOGGING

A table marked as LOGGING will generate redo in the Oracle Database - Redo Log (Transaction Log Files) while a table marked as Oracle Database - NOLOGGING will bypass it.

alter table big_table logging;

NOLOGGING

Oracle Database - NOLOGGING





Discover More
Card Puncher Data Processing
Oracle Database - Direct (path insert|load) (/*+ APPEND */)

A direct-path insert is also known as: direct load A direct-path insert is a bulk operation which will only bypass redo log generation in three cases : the database is in NOARCHIVELOG mode database...
Card Puncher Data Processing
Oracle Database - How to bypass the redo log generation ?

A direct path insert will only bypass Redo Log generation in two cases : the database is in NOARCHIVELOG Mode the operation is performed on a table marked as NOLOGGING The insert /+ APPEND / will...
Card Puncher Data Processing
Oracle Database - Redo Log (Transaction Log Files)

transaction log in Oracle are knwon as the redo log. Every instance of an Oracle Database has an associated redo log to protect the database in case of an instance failure. To protect against a failure...
Card Puncher Data Processing
Oracle Database - Why you have still a lot of redo and archive ? The Index side effect.

You use the direct path insert and set the logging mode as NOLOGGING but you have still a lot of redo log generated. Why ? The answer is that you have an index on the table, and the index cannot just...



Share this page:
Follow us:
Task Runner