|
Any tablespace that goes into hot backup mode and is subsequently used for
recovery would need redo logs applied. If your processes were doing
direct insert without logging then this data would not be available.
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).
|
