ORA-1578 is indication of physical block corruption. Oracle computes an internal checksum before fetching the block from disk, when it is about to fetch the block it reads the block header and compare the checksum stored in it. If the checksum mismatches we get ora-1578 error.
It indicates that a block is corrupted at hardware level i.e at OS.
This error will always come whenever the corrupted block is read by Oracle.
Reasons for ora-1578:
1. Bad sectors in the Storage Disk Drive.
2. Formatting of blocks At OS level.( Zeroed out disk blocks).
3. some corruption in underlying hardware which is making block unreadable.
How to collect information for ora-1578:
ORA-01578: ORACLE data block corrupted (file # 14, block # 38976)
The block # 38976 shows the corrupted block number and the file # 14 indicates
the reletive file number 14.
1. Get the absolute file number:
To get the absolute file # we will use the following query:
SQL > select file# from v$datafile where rfile#=14;
here the absolute file# is also 14.
2. Get the segment name and segment type in which this corrupted block resides:
Use the following query:
SQL > SELECT tablespace_name, segment_type, owner, segment_name FROM
dba_extents WHERE file_id = 14 and 38976 between block_id AND block_id + blocks – 1;
— It will give us the segment type (Table, Index, LOB etc.), name of the segment (Table name
Index name etc.), Owner of the segment and the tablespace name of the segment in which corrupted block resides.
SQL > select FILE#,TS#,STATUS,BLOCKS,NAME from v$datafile where FILE#=14;
— From this we will get the tablespace number and the fine name of the datafile in which the corrupted block resides.
SQL> select TS#,NAME from v$tablespace where TS#=;
— It will give us the Name of the tablespace.
Now we have all the information required to perform an action to overcome ora-1578.
I will be providing more on this about solving ora-1578 soon.