RE: v$backup_corruption - FRACTURED vs. LOGICAL & Solutions

Chris,

Thanks for the reply,
the ORA- errors references,
the (surprising) "DBMS_REPAIR" and/or "DBVERIFY" comments, and Metalink note 28814.1 reference.

I thought DBMS_REPAIR fixed Logical Corruption...but I have not experience with it.

Chris Marquez
Oracle DBA

-----Original Message-----
From: Christian Antognini [mailto:Christian.Antognini_at_trivadis.com] Sent: Wed 8/10/2005 5:51 PM
To: Marquez, Chris
Cc: oracle-l_at_freelists.org
Subject: RE: v$backup_corruption - FRACTURED vs. LOGICAL & Solutions  

Hi Chris  

>What is the meanings for "FRACTURED" & "LOGICAL" values
>in the CORRUPTION_TYPE column of the v$backup_corruption view.
 

FRACTURED ==> physical corruption  

Oracle is not able to read or write a block; if the block can be read, its content makes no sense.

Usually due to hardware failures.

Typical symptoms:
- ORA-00600: internal error code
- ORA-01578: ORACLE data block corrupted  

LOGICAL ==> logical corruption  

Inconsistency within the data.

Usually due to Oracle bugs.

Typical symptoms:

- ORA-00600: internal error code
- ORA-01498: block check failure
- ORA-01499: table/index cross reference failure

 

>How could "DBMS_REPAIR" and/or "DBVERIFY" be used to validate
>and fix any corruption we might have.
 

These two utilities don't fix problems!    

Give a look to Metalink note 28814.1. It's a good starting point...      

Good luck,

Chris

--
http://www.freelists.org/webpage/oracle-l