Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Mapping block # to object - we have block corruption

chuckersApr 4 2007 — edited Apr 5 2007

Our SAN was getting low on space (1.8Gb left or so) and we started getting msgs in the alert log like

ORA-3297 signalled during: ALTER DATABASE DATAFILE '/u02/oradata/dev/claims_m...

I wasn't able to find out what these error msgs actually meant, but I think I know now. We took a cold backup, extended the amount of space available on the SAN, and restarted the database. When it came up, it signalled that there were about 70 corrupt blocks, which we found after running

RMAN> BACKUP VALIDATE DATABASE ARCHIVELOG ALL;

and then

SQL> select *
  2  from v$database_block_corruption;
 
     FILE#     BLOCK#     BLOCKS CORRUPTION_CHANGE# CORRUPTIO
---------- ---------- ---------- ------------------ ---------
         1      63550          1                  0 CHECKSUM
         2      31878          1                  0 CHECKSUM
         2      91205          1                  0 FRACTURED
...

So the sol'n on metalink is to export the problem objects and then import them, but I don't know how to map the BLOCK# to the object it belongs to. Could someone help me with that query?

-Thanks
Chuck

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on May 3 2007
Added on Apr 4 2007
4 comments
861 views