LOGGING| NOLOGGING

最新推荐文章于 2024-06-06 07:05:08 发布

转载最新推荐文章于 2024-06-06 07:05:08 发布 · 612 阅读

收录于

oracle

当前文章被收录于：

oracle

14 篇文章 0 人学习

订阅专栏查看详情

当前文章被以下社区和专栏收录：

本文介绍了ORACLE数据库中LOGGING与NOLOGGING属性的作用及适用场景。NOLOGGING模式下，数据修改仅进行最小化记录，适用于特定DML与DDL操作。文章强调了在NOLOGGING模式下操作后的备份必要性。

LOGGING| NOLOGGING specifies the default logging attributes of all tables, indexes, and partitions within the tablespace. LOGGING is the default.

The tablespace-level logging attribute can be overridden by logging specifications at the table, index, and partition levels.

Only the following operations support the NOLOGGING mode:

DML: direct-load INSERT (serial or parallel), Direct Loader (SQL*Loader)

DDL: CREATE TABLE ... AS SELECT, CREATE INDEX, ALTER INDEX ... REBUILD, ALTER INDEX ... REBUILD PARTITION, ALTER INDEX ... SPLIT PARTITION, ALTER TABLE ... SPLIT PARTITION, and ALTER TABLE ... MOVE PARTITION

In NOLOGGING mode, data is modified with minimal logging (to mark new extents INVALID and to record dictionary changes). When applied during media recovery, the extent invalidation records mark a range of blocks as logically corrupt, because the redo data is not logged. Therefore, if you cannot afford to lose the object, you should take a backup after the NOLOGGING operation.