Take
advantage of the efficiencies of the NOLOGGING attribute of tables and indexes
if you can. When you create a table as NOLOGGING, no redo data is written to
the redo stream to support the creation of the object. This is useful for
making large inserts go faster.
If you
perform media recovery, and there are NOLOGGING objects involved, they will be
marked logically corrupt during the recovery process. In this case, drop the
NOLOGGING objects and re-create them.
