Home
All Oracle Error Codes
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

Re: Help - Corrupted Block - Lob Segment - NOLOGGING

Dennis Williams

2006-10-23

Replies:
Sam,
 
First, I would get on the vendor of this product very hard. Have your manager or even higher escalate it to somebody at the vendor with enough authority to ensure the resources to solve the problem. They may be able to help. If not, at least you've illuminated where the problem lies, namely with the vendor. This is not a time to suffer in silence. One question for them is whether your users should still be using this application while experiencing these problems.
 
Here is a pretty good article (at least at first glance) that discusses data corruption.
http://www.quest-pipelines.com/newsletter-v4/0103_C.htm
 
One thing you might consider is writing a program that will move the data from this table to another table. Give it the capability to continue when it encounters an error (when it hits a bad block), and log the errors. This way you can save what you can. Maybe the vendor will provide a way to recover more data.
 
Good luck,
Dennis Williams