Oracle Database / Storage, Undo & Redo
ORA-01578: preserve evidence of a corrupt Oracle block
A block-corruption report needs file and block identifiers, affected objects and storage context. Avoid unplanned repair that could discard data.
Environment and inputs: Oracle Database 19c baseline · SQL*Plus-compatible SQL unless RMAN, DGMGRL, ADRCI or a host shell is specified. Check release, patch level, edition and container first.
Start with this diagnostic
Use the stated SQL, RMAN, DGMGRL or host shell and replace sample names with approved targets. DBA and V$ views need authorized catalog access in the correct container. Do not grant broad privileges for an example.
SELECT file#, block#, blocks, corruption_type FROM v$database_block_corruption;Read the result
The view reports corruption known to the database through relevant checks. An empty result does not rule out a block failure that has not been recorded here.
Resolve and verify
Map the reported block to its segment using the DBA's approved procedure, validate backup availability and engage the recovery team or Oracle Support for a precise recovery plan.
Operational precautions
Do not skip corrupt blocks, rebuild critical objects or invoke repair packages without assessing data loss and recoverability.