I was going through below note.
Force Logging Allows NOLOGGING Mark on Objects (Doc ID 1264965.1)
Which says in goal as below
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;
but in the solution it says contradictory statement as below.
This setting takes precedence over and is independent of any NOLOGGING or FORCE LOGGING settings you specify for individual tablespaces and any NOLOGGING settings you specify for individual database objects.
my experience with dataguard setup is that if we put the primary database in force logging mode and then create a table with nologging mode, the standby reports below errors which is consistent with Goal of the note.
ORA-01578 ORA-01110 ORA-26040
Does anybody had similar experience?