Select 'dbv file=' || name || ' blocksize='|| block_size || ' logfile=' || You can use the below command to generate the dbv command for all the datafiles sqlplus /nolog dbv file=datafile_name blocksize=datafile_block_size You can also use dbverify utility to identify Physical and Logical Intra Block Corruptions. For ex:- ORA-01578: ORACLE data block corrupted (file # 11, block # 45) log file for corrupted blocks, data file list. Please note, After a corrupt block is repaired, the row identifying the block is deleted from the view.Ĭhecking alert log for possible occurrenceĬheck alert. &BLOCK_ID BETWEEN BLOCK_ID AND BLOCK_ID + BLOCKS - 1 SQL> SELECT TABLESPACE_NAME, SEGMENT_NAME, PARTITION_NAME, SEGMENT_TYPE SQL> select * from v$database_block_corruption Select the view to identify the corrupted blocks detected by RMAN. We can use below command in case we want to do checking selectively BACKUP VALIDATE DATAFILE 1 īACKUP VALIDATE check logical DATAFILE 1 īACKUP VALIDATE check logical TABLESPACE TOOLS “CHECK LOGICAL” option is used to identify both Physical and Logical Block Corruptions. Run below command RMAN> backup validate check logical database
Checking alert log for possible occurrence ORA-00600 – This error is related to block corruption, and occurs due to a higher SCN than of database SCN.ĭatabase corruption can be find using the below methodĬ. ORA-08103 – This error is a logical corruption error for a particular data block.