Links
• Home
• Oracle DBA Forum
Frequent Oracle Errors
•TNS:could not resolve the connect identifier specified
•Backtrace message unwound by exceptions
•invalid identifier
•PL/SQL compilation error
•internal error
•missing expression
•table or view does not exist
•end-of-file on communication channel
•TNS:listener unknown in connect descriptor
•insufficient privileges
•PL/SQL: numeric or value error string
•TNS:protocol adapter error
•ORACLE not available
•target host or object does not exist
•invalid number
•unable to allocate string bytes of shared memory
•resource busy and acquire with NOWAIT specified
•error occurred at recursive SQL level string
•ORACLE initialization or shutdown in progress
•archiver error. Connect internal only, until freed
•snapshot too old
•unable to extend temp segment by string in tablespace
•Credential retrieval failed
•missing or invalid option
•invalid username/password; logon denied
•unable to create INITIAL extent for segment
•out of process memory when trying to allocate string bytes
•shared memory realm does not exist
•cannot insert NULL
•TNS:unable to connect to destination
•remote database not found'>ora-02019
•exception encountered: core dump
•inconsistent datatypes
•no data found
•TNS:operation timed out
•PL/SQL: could not find program
•existing state of packages has been discarded
•maximum number of processes exceeded
•error signaled in parallel query server
•ORACLE instance terminated. Disconnection forced
•TNS:packet writer failure
•see ORA-12699
•missing right parenthesis
•name is already used by an existing object
•cannot identify/lock data file
•invalid file operation
•quoted string not properly terminated
v$backup_corruption - FRACTURED vs. LOGICAL & Solutions

v$backup_corruption - FRACTURED vs. LOGICAL & Solutions

2005-08-11       - By Marquez, Chris

Reply:     1     2     3  


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@(protected)]
Sent: Wed 8/10/2005 5:51 PM
To: Marquez, Chris
Cc: oracle-l@(protected)
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 (See ORA-00600.ora-code.com): internal error code
- ORA-01578 (See ORA-01578.ora-code.com): ORACLE data block corrupted



LOGICAL ==> logical corruption



Inconsistency within the data.

Usually due to Oracle bugs.

Typical symptoms:
- ORA-00600 (See ORA-00600.ora-code.com): internal error code
- ORA-01498 (See ORA-01498.ora-code.com): block check failure
- ORA-01499 (See ORA-01499.ora-code.com): 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



<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7232.39">
<TITLE>RE: v$backup_corruption - FRACTURED vs. LOGICAL &amp; Solutions</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>

<P><FONT SIZE=2>Chris,<BR>
<BR>
Thanks for the reply,<BR>
the ORA- errors references,<BR>
the (surprising) &quot;DBMS_REPAIR&quot; and/or &quot;DBVERIFY&quot; comments,
<BR>
and Metalink note 28814.1 reference.<BR>
<BR>
I thought DBMS_REPAIR fixed Logical Corruption...but I have not experience with
it.<BR>
<BR>
Chris Marquez<BR>
Oracle DBA<BR>
<BR>
<BR>
<BR>
-- --Original Message-- --<BR>
From: Christian Antognini [<A HREF="mailto:Christian.Antognini@(protected)"
>mailto:Christian.Antognini@(protected)</A>]<BR>
Sent: Wed 8/10/2005 5:51 PM<BR>
To: Marquez, Chris<BR>
Cc: oracle-l@(protected)<BR>
Subject: RE: v$backup_corruption - FRACTURED vs. LOGICAL &amp; Solutions<BR>
<BR>
Hi Chris<BR>
<BR>
<BR>
<BR>
&gt;What is the meanings for &quot;FRACTURED&quot; &amp; &quot;LOGICAL&quot;
values<BR>
&gt;in the CORRUPTION_TYPE column of the v$backup_corruption view.<BR>
<BR>
<BR>
<BR>
FRACTURED ==&gt; physical corruption<BR>
<BR>
<BR>
<BR>
Oracle is not able to read or write a block; if the block can be read, its
content makes no sense.<BR>
<BR>
Usually due to hardware failures.<BR>
<BR>
Typical symptoms:<BR>
- ORA-00600 (See ORA-00600.ora-code.com): internal error code<BR>
- ORA-01578 (See ORA-01578.ora-code.com): ORACLE data block corrupted<BR>
<BR>
<BR>
<BR>
LOGICAL ==&gt; logical corruption<BR>
<BR>
<BR>
<BR>
Inconsistency within the data.<BR>
<BR>
Usually due to Oracle bugs.<BR>
<BR>
Typical symptoms:<BR>
- ORA-00600 (See ORA-00600.ora-code.com): internal error code<BR>
- ORA-01498 (See ORA-01498.ora-code.com): block check failure<BR>
- ORA-01499 (See ORA-01499.ora-code.com): table/index cross reference failure<BR>
<BR>
<BR>
<BR>
&gt;How could &quot;DBMS_REPAIR&quot; and/or &quot;DBVERIFY&quot; be used to
validate<BR>
&gt;and fix any corruption we might have.<BR>
<BR>
<BR>
<BR>
These two utilities don't fix problems!<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
Give a look to Metalink note 28814.1. It's a good starting point...<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
Good luck,<BR>
<BR>
Chris<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>