Detecting Corruption: DBVERIFY versus RMAN backup validate check logical database
Hello @,
I have deliberately corrupted some empty blocks on my crash&burn Oracle instance.
Now when I run DBVERIFY it reports these three blocks as being corrupt.
What makes me wonder is that I can run RMAN "backup validate check logical database"
as often as I want, but the view V$DATABASE_BLOCK_CORRUPTION remains empty.
The views V$BACKUP_CORRUPTION and V$COPY_CORRUPTION also give no
hint about the corrupt blocks.
Are the RMAN logical checks less stringent than the DBVERIFY checks?
After all, only freespace is affected so one could argue wether there is really some corruption inside the database or not.
I have deliberately corrupted some empty blocks on my crash&burn Oracle instance.
Now when I run DBVERIFY it reports these three blocks as being corrupt.
What makes me wonder is that I can run RMAN "backup validate check logical database"
as often as I want, but the view V$DATABASE_BLOCK_CORRUPTION remains empty.
The views V$BACKUP_CORRUPTION and V$COPY_CORRUPTION also give no
hint about the corrupt blocks.
Are the RMAN logical checks less stringent than the DBVERIFY checks?
After all, only freespace is affected so one could argue wether there is really some corruption inside the database or not.
0