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

corrupt datafile

Terry Sutton


A new client has a serious corruption error.  During a hot backup (not RMAN) Thursday morning it was discovered that a datafile was corrupted on the disk.  When the database is started up, the following error occurs:
"ORA-01122: database file 5 failed verification check
ORA-01110: data file 5:
ORA-01251: Unknown File Header Version read for file number 5"
When dbverify is run against this file, every block is indicated as corrupt, which isn't surprising.
We have a copy of the datafile from Wednesday's hot backup, but they don't have the archivelogs necessary to sync this datafile with the rest of the database.  And we don't have the other datafiles from Wednesday's backup, so we can't just go back to the state the database was in then.
Any ideas on what they can do?  I can't think of anything (other than going back to an export they have from 6 months ago, which seems to be the only historical backup they have).