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.
扫一扫
2195
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
