Re: Tracking down NOLOGGING objects

On top of Riyaj Shamsudeen's excellent posting, I want to add that Note:1031381.6 (How do I Dump Redo Log File Information?) describes various ways to dump logfiles. If you need to use the time option, you also need Note:1020342.6 (CONVERT MM/DD/YYYY HH:MI:SS TO REDO DUMP TIME) and Note:1020343.6 (CONVERT REDO DUMP TIME TO MM/DD/YYYY HH:MI:SS). Commonly seen layers in redo dump are 5 for Transaction Undo, 10 for Index and 11 for table data. 19 is direct load related. 19.2 is for invalidation redo. This concept is briefly mentioned in Data Warehousing guide of documentation: "NOLOGGING allows the direct-path INSERT operation to generate a negligible amount of redo (range-invalidation redo, as opposed to full image redo)". It's like some "meta" information saying blocks from X to Y are missing actual redo data.

Yong Huang       

--
http://www.freelists.org/webpage/oracle-l