Database Tutorials MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux 
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.
We can use it for the following operations.
1 2 3 4 5 6 7 8 9 10 11 | CREATE TABLE ALTER TABLE CREATE INDEX CREATE MATERIALIZED VIEW ALTER MATERIALIZED VIEW CREATE MATERIALIZED VIEW LOG ALTER MATERIALIZED VIEW LOG CREATE TABLESPACE ALTER TABLESPACE CREATE INDEX .. REBUILD ALTER TABLE .. MOVE |
You can find Sample Usage below.
All objects that will be created in the following tablespace will default to the LOGGING structure.
In other words, the operations to be performed on these objects will be logged in the redo log.
1 2 3 4 5 6 7 8 | CREATE TABLESPACE TABLESPACE_NAME DATAFILE '+DISKGROUP_NAME' SIZE 1024K AUTOEXTEND ON NEXT 100M MAXSIZE UNLIMITED LOGGING ONLINE EXTENT MANAGEMENT LOCAL AUTOALLOCATE BLOCKSIZE 32K SEGMENT SPACE MANAGEMENT AUTO FLASHBACK ON; |
