Remember only certain operations make use of the nologging option. Some of these are a direct load with SQL*Loader or a direct load insert. The direct load insert is a special form of the insert statement that uses the /*+ append */ hint.
That means that ordinary inserts, updates and deletes always generate redo, no matter if the underlying table or index is specifed with nologging or not.
Nologging can be overridden at tablespace level using alter tablespace ... force logging.
Nologging has no effect if the database is in force logging mode (which can be controlled with alter database force [no] logging mode).
Dig Deeper on Oracle SOA
Related Q&A from Harish Harbham
SOA and Integration expert Harish Harbham explains how to transfer data from Oracle to MS SQL Server. Continue Reading
Oracle expert Harish Harbham explains how Oracle Streams can be used for replication. Continue Reading
Expert Harish Harbham answers the question, "How do you convert SQL Server 2005 database into 0racle 10g?" Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.