Can someone explain FORCE LOGGING mode to me?
raindogNov 27 2010 — edited Nov 27 2010So, for 11.2, let's say I have a database that is not in FORCE LOGGING mode (v$database shows "NO" for FORCE_LOGGING).
I did an ALTER DATABASE FORCE LOGGING, then did a CREATE TABLE ... NOLOGGING as a user and the statement worked just fine.
I also notice that all of my tablespaces are still listed "NO" for force_logging, and there are 114 tables (owned by MDSYS, SYSTEM, SYSMAN, etc.) where LOGGING is set to NO.
So how does it work when you have the database FORCE LOGGING set to YES?
Is it the case that:
- the database setting (as shown in V$DATABASE) overrides all tablespace and segment settings
- if the database setting was ever changed to NO FORCE LOGGING, then these existing tablespace and segment settings would once again be significant, but as long as the database-wide FORCE_LOGGING is set to YES, they are meaningless