Thursday, July 5, 2018

Fractured block found during backing up datafile


This error means that RMAN found an inconsistent block during the backup of a datafile. It is quite likely that on second attempt to read the block, RMAN is able to find a consistent image of the block, hence no further action would be required. But, if you need to perform a block recovery, this article will be worth reading. Alert log file will show message similar to the following when this error is reported.

Thread 1 advanced to log sequence 77385 (LGWR switch)
  Current log# 5 seq# 77385 mem# 0: /data/mydatabase/redo05.log
Thu Jun 28 01:04:18 2018
Archived Log entry 154451 added for thread 1 sequence 77384 ID 0xd7da387f dest 1:
Thu Jun 28 01:05:59 2018
Hex dump of (file 6, block 756988) in trace file /u01/app/oracle/diag/rdbms/mydatabase/mydatabase/trace/mydatabase_ora_672.trc
Corrupt block relative dba: 0x018b8cfc (file 6, block 756988)
Fractured block found during backing up datafile
Data in bad block:
 type: 6 format: 2 rdba: 0x018b8cfc
 last change scn: 0x0000.ab9059fc seq: 0x1 flg: 0x06
 spare1: 0x0 spare2: 0x0 spare3: 0x0
 consistency value in tail: 0x0e960601
 check value in block header: 0x972b
 computed block checksum: 0x576a
Reread of blocknum=756988, file=/data/mydatabase02.dbf. found valid data
Thu Jun 28 01:18:50 2018
Thread 1 advanced to log sequence 77386 (LGWR switch)
  Current log# 6 seq# 77386 mem# 0: /redo/mydatabase/redo06.log
Thu Jun 28 01:18:53 2018
Archived Log entry 154453 added for thread 1 sequence 77385 ID 0xd7da387f dest 1:
Thu Jun 28 01:29:45 2018
Thread 1 advanced to log sequence 77387 (LGWR switch)
  Current log# 7 seq# 77387 mem# 0: /data/mydatabase/redo07.log
Thu Jun 28 01:29:47 2018
Archived Log entry 154455 added for thread 1 sequence 77386 ID 0xd7da387f dest 1:
Thu Jun 28 01:44:05 2018

Corrupt block relative dba

Error stack starts with this error message showing the file number and block number that was found inconsistent/corrupt.

Reread of blocknum=756988, file=/data/mydatabase02.dbf. found valid data

This message at the end of the error stack shows that RMAN was able to find a consistent copy of the databblock. Since RMAN has found the block valid, no further action or block recovery is needed.

Reread of rdba: 0x01415010 (file 5, block 86032) found same corrupted data

When re-reading of block once again found the block inconsistent, it would mean that block is really corrupted and block media recovery is needed.

No comments:

Post a Comment

Popular Posts - All Times