v$backup_corruption - FRACTURED vs. LOGICAL & Solutions

Links

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-10 - By Christian Antognini

Reply: 1 2 3

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

<html>

<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<meta name=Generator content="Microsoft Word 11 (filtered)">
<style>

</style>

</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

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&
#8217;s
a good starting point...

 

 

 

Good luck,

Chris

</div>

</body>

</html>