The size of a redo log generated for an operation in NOLOGGING mode is significantly smaller than the log generated in LOGGING mode.
The NOLOGGING clause causes minimal redo information to be generated during the table creation. And direct-path inserts will not be logged.
However, DML statements (UPDATE, DELETE, and conventional path insert) are unaffected by the NOLOGGING attribute of the table and generate redo.
If the object for which you are specifying the logging attributes resides in a database or tablespace in force logging mode, then Oracle Database ignores any NOLOGGING setting until the database or tablespace is taken out of force logging mode.
The NOLOGGING clause causes minimal redo information to be generated during the table creation. And direct-path inserts will not be logged.
However, DML statements (UPDATE, DELETE, and conventional path insert) are unaffected by the NOLOGGING attribute of the table and generate redo.
If the object for which you are specifying the logging attributes resides in a database or tablespace in force logging mode, then Oracle Database ignores any NOLOGGING setting until the database or tablespace is taken out of force logging mode.
本文探讨了NOLOGGING模式下数据库操作的特点,指出在这种模式下产生的重做日志相较于LOGGING模式要小得多。NOLOGGING模式在创建表时会生成最小的重做信息,并且直接路径插入不会被记录。然而,对于DML语句如更新、删除及常规路径插入等,即使表具有NOLOGGING属性,仍然会产生重做日志。
255

被折叠的 条评论
为什么被折叠?



