The main question about NOLOGGING I hear all the time is: Does creating a table with the NOLOGGING option means there is "no generation of redo ever," or just that the initial creation operation has no redo generation, but that DML down the road generates redo? How and when can the NOLOGGING option be employed? Redo generation is a vital part of the Oracle recovery mechanism. Without it, an instance will not recover when it crashes and will not start in a consistent state. Excessive redo generation is the result of excessive work on the database. This presentation covers the subject of reducing redo generation using LOGGING and NOLOGGING options, the differences between them, how it happens, how to reduce it, and when to use. Examples and tips regarding each one will be provided.

This is a free webcast, but you have to register to attend.

Check out the webcast schedule here.