> Direct-path INSERT operations (except for dictionary updates) never generate undo logs. The > NOLOGGING attribute does not affect undo, only redo. To be precise, NOLOGGING allows the > direct-path INSERT operation to generate a negligible amount of redo (range-invalidation redo, as > opposed to full image redo). Note:290161.1 says "Invalidation redo containing information about the nologging operation and the range of blocks it affects". http://www.freelists.org/archives/o...5/msg01111.html says "NOLOGGING affects recovery only if that operation generates block range invalidation redo records." It looks like range invalidation redo is some high level (maybe called meta) info about the change to the physical database, such as operation type, range of blocks affected. But it does not contain actual data (i.e. no before image for update, no rowid for insert, no whole-row data for delete). It cannot be used to re-construct a SQL in logminer. [Original message at http://www.itpub.net/thread-600830-1-1.html]