Block Corruption on Physical Standby

Block Corruption on Physical Standby in Oracle 11g Database

Possible Errors Codes-

ORA-00600: internal error code, arguments
ORA-10567: Redo is inconsistent with data block (file #, block# )
ORA-10564: tablespace tablespace_name
ORA-01110: data file 55: 'data_file_name.dbf'
ORA-10561: block type 'TRANSACTION MANAGED INDEX BLOCK', data object#

Possible Cause- 

These errors occur when block corruption replicates from the primary database to the Physical Standby database through archived logs. Immediately after getting replicated these archived logs are being read by the ongoing recovery process (control file gets updated). The recovery process gets halt when it starts reading the corrupted block from the archived log.  This scenario is being supported by the following values for the given parameters.

DB_BLOCK_CHECKING ( Low| Medium | Full )  

DB_BLOCK_CHECKSUM ( Typical | Full )

DB_LOST_WRITE_PROTECT ( Typical | Full )

Possible Solution - 

In case you keep restarting recovery without solving this block thing it will keep killing the PMON process and then you have to bring database instance up every time to restart the recovery process.

To keep going with recovery just update the above-shown parameters to the following values in the database MOUNT stage and then start the recovery process.

DB_BLOCK_CHECKING ( Off )  

DB_BLOCK_CHECKSUM ( Off )

DB_LOST_WRITE_PROTECT ( None)

In case your setup has ACTIVE STANDBY on the place then open database READ ONLY after the MOUNT stage and start the recovery process.