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: corrupt datafile

Terry Sutton



Good idea. The client was actually trying stuff along this line, and it's
what they're using to get what data they can. Unfortunately they'll lose a
pretty significant amount of data, but that's the risk of not having



> Terry,
> For point-in-time recovery you would also need the RBS/UNDO tablespace(s)
> allow incomplete transactions to be rolled back. Moot point considering
> spread of datafiles in backups and lack of archive logs.
> Based on the premise that some data is better than no data (and the
> assumption that the indexes are in a non-corrupted tablespace), you could
> take the affected datafile offline, open the database and dump the data
> is in the indexes into copies of the tables then dump the data to an
> dump file. It's not ideal (unless you have indexes that cover all columns)
> but it may help application analysts/management recover a large amount of
> usable data. Or it may not, depends entirely on the coverage/availability
> indexes and the relative importance of non-indexed fields (probably
> important or else they wouldn't be there!).
> This would often be a reasonable approach for reconstructing small amounts
> of data following block corruption (pre-RMAN blockrecover) but when you
> don't have many options it may be that it saves "some" business data.

Please see the official ORACLE-L FAQ: http://www.orafaq.com
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe' in the subject line.
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html