Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: v$backup_corruption - FRACTURED vs. LOGICAL & Solutions

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

From: Christian Antognini <Christian.Antognini_at_trivadis.com>
Date: Wed, 10 Aug 2005 23:51:47 +0200
Message-ID: <F2C9CCA71510B442AF71446CAE8AEBAF0AC02F@MSXVS04.trivadis.com>


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
Received on Wed Aug 10 2005 - 16:54:25 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US