<\/p>\n
With the logging_clause parameter, we can specify whether the database objects are to be logged in the redo log when they are created, using LOGGING or NOLOGGING.<\/p>\n
We can use it for the following operations.<\/p>\n
CREATE TABLE\r\nALTER TABLE\r\nCREATE INDEX\r\nCREATE\u00a0MATERIALIZED\u00a0VIEW\r\nALTER MATERIALIZED\u00a0VIEW\r\nCREATE\u00a0MATERIALIZED\u00a0VIEW\u00a0LOG\r\nALTER MATERIALIZED\u00a0VIEW\u00a0LOG\r\nCREATE\u00a0TABLESPACE\r\nALTER TABLESPACE\r\nCREATE\u00a0INDEX\u00a0..\u00a0REBUILD\r\nALTER\u00a0TABLE ..\u00a0MOVE<\/pre>\n<\/p>\n
You can find Sample Usage below.<\/p>\n
All objects that will be created in the following tablespace will default to the LOGGING structure.<\/p>\n
In other words, the operations to be performed on these objects will be logged in the redo log.<\/p>\n
CREATE TABLESPACE TABLESPACE_NAME DATAFILE\r\n'+DISKGROUP_NAME' SIZE 1024K AUTOEXTEND ON NEXT 100M MAXSIZE UNLIMITED\r\nLOGGING\r\nONLINE\r\nEXTENT MANAGEMENT LOCAL AUTOALLOCATE\r\nBLOCKSIZE 32K\r\nSEGMENT SPACE MANAGEMENT AUTO\r\nFLASHBACK ON;<\/pre>\n\n<\/div>\n