Blog

Force logging and NOLOGGING clauses

Today we had an odd case whereby we could see a large number of indexes that were reporting they had been created with a NOLOGGING clause, however the DB is in FORCE LOGGING mode. Time for a quick test to see what was going on and whether we should actually be worried or not about our standby.

First test – create a table with NOLOGGING clause while FORCE LOGGING is on:

Summary

If you create any object when FORCE LOGGING is turned on it WILL write it to redo, but for some reason the LOGGING column will show as ‘NO’ on the object tables. Strange and unexpected behaviour but it does mean we can relax about our standby now.