Block corruption due to NOLOGGING

If a NOLOGGING (or UNRECOVERABLE) operation is performed on an object and the datafile containing that object is subsequently recovered, then the data blocks affected by the NOLOGGING operation are marked as corrupt and will signal an ORA-1578 error when accessed. In Oracle 8i, an ORA-26040 is also signaled (ORA-26040: Data block was loaded using the NOLOGGING option) which makes the cause fairly obvious, but earlier releases have no additional error message. If a block is corrupt due to recovery through a NOLOGGING operation, you need to understand that:

If this is your situation, please note that:

Currently in Oracle 9i and Oracle 10g R1, only the primary database v$datafile view reflects NOLOGGING operations. In Oracle 10g R2, the v$datafile view was enhanced to include information regarding when an invalidation redo is applied and the aforementioned corrupted blocks are written to the corresponding datafile on a Redo Apply (or media recovery or standby) instance.