A block in which the header and footer are not consistent at a given SCN. In a user-managed backup, an operating system utility can back up a datafile at the same time that DBWR is updating the file. It is possible for the operating system utility to read a block in a half-updated state, so that the block that is copied to the backup media is updated in its first half, while the second half contains older data. In this case, the block is fractured.

For non-RMAN backups, the ALTER TABLESPACE … BEGIN BACKUP or ALTER DATABASE BEGIN BACKUP command is the solution for the fractured block problem. When a tablespace is in backup mode, and a change is made to a data block, the database logs a copy of the entire block image before the change so that the database can reconstruct this block if media recovery finds that this block was fractured.

The block that the operating system reads can be split, that is, the top of the block is written at one point in time while the bottom of the block is written at another point in time. If you restore a file containing a fractured block and Oracle reads the block, then the block is considered a corrupt.

What Happens When A Tablespace/Database Is Kept In Begin Backup Mode (Doc ID 469950.1)

1. For checking the Oracle Database from corruption/Fractured block.

2. Following block show the block id,file id, type of corruption after RMAN command

3. Find the object_name,object_type from following view:

4. If you find fractured block in free space then you follow oracle(Doc ID 336133.1)

First option:
According to this doc id, for remove the fractured block in free space. you need
to write on that block then it will automatically fixed the issue.

After getting error rerun the validate command for rman for verify

Second option:
You create one new tablespace and move the objects from that tablespace to new tablespace and resize the datafile which having fractured block.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.