This preview shows page 1. Sign up to view the full content.
Unformatted text preview: : C
To reduce redo logs generating a DBA would load a table during a direct loaded
operation using the NOLOGGING options. Specifying the NOLOGGING clause means
that the creation of the table or index, as well data loaded into the table or index, will not
generate any redo information. This enhances performance of data load or object creation
operations, but leaves you with dilemma later if the database fails and you haven't taken a
backup. Even if you archive your redo logs, you still will not be able to recover data,
because no redo was generated for operations related to that object. Use NOLOGGING
very sparingly, and only with table data load or index creation operations when you plan
to take a backup very soon anyway.
A: Using the NOLOGGING option does not eliminate further backup, quite the contrary it
requires DBA to take backup as soon as possible after load operations completion.
B: This option disable temporarily redo log generation, not collecting statistics.
View Full Document
This document was uploaded on 03/08/2014.
- Fall '09