Skip to Main Content

Allow handling NOLOGGING tables after recovery

bargenDec 11 2014 — edited Jan 11 2016

After a database recovery, it is a common problem that an application run into the error messages

ORA-01578: ORACLE data block corrupted and

ORA-26040: Data block was loaded using the NOLOGGING option

as soon as it tires to access a NOLOGGING table (which may be hours our days later).

Oracle RDBMS should prevent this situation in one of the following ways:

Either by supporting a keyword like ON RECOVER TRUNCATE or similar on table creation (preferred),

or by providing a trigger that runs after database recovery (why not call it AFTER RECOVERY ON DATABASE)

and a dbms_% procedure that truncates all NOLOGGING tables in a given schema.

Post Details
Added on Dec 11 2014