FORCE LOGGING Mode in Oracle

In force logging mode, the Oracle database must write the redo records even when NOLOGGING is used with DDL statements.
It will force the write of REDO records even when NOLOGGING is specified.

If we write the NOLOGGING option with DDL commands, then our database will not generate redo for those DDLs, but in the case of Data Guard or media recovery, it has a negative impact. So before implementing Data Guard or a standby server, we need to enable the FORCE LOGGING mode of the Oracle Database.
So every change should be recorded and updated in the standby server while syncing.

Force Logging is turned on for the tablespace and database.

Note:
–The FORCE LOGGING mode is a persistent attribute if the database is shut down and restarted, it remains in the same logging mode as configured.
–Re-create the control file, the database is not restarted in the FORCE LOGGING mode unless you specify the FORCE LOGGING clause in the CREATE CONTROL FILE statement.

Check database force logging

select force_logging from v$database;

Enable the Database force logging

ALTER DATABASE FORCE LOGGING;

Disable the Database force logging

ALTER DATABASE NO FORCE LOGGING;

Check tablespace force logging

select force_logging from dba_tablespaces;

Enable tablespace force logging

ALTER TABLESPACE FORCE LOGGING;

Disable tablespace force logging

ALTER TABLESPACE NO FORCE LOGGING;