Force Logging Allows NOLOGGING Mark on Objects
(Doc ID 1264965.1)
Last updated on DECEMBER 19, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.4 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Generic (Platform Independent)
***Checked for relevance on 01-Dec-2016***
If you enable force logging on the database you can still create an object with nologging attributes and dba_tables shows that the object has nologging status:
SQL> alter database force logging;
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document