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

ORA-4030 Question -

Post, Ethan


Anyone ever heard of this happening...a 4030 error that is not a real
4030 error? The client is a powerbuilder app running in a citrix
environment? Is it possible to trigger a 4030 error on the client side
within a PB application? This didn't make a lot of sense to me.=20

Oracle states that this was not an ora-4030 error. A 4030 error is a
server side error and as such we would have received errors in the alert
log, a trace file with a
heap dump and very possibly a core dump. We have none of those. The
trace file that was generated does not contain a heap dump and basically
has no
information that Oracle can look at to determine the problem. He
stated that it appeared that the client software thought it had received
an out-of-memory error=20
and so reported it as a 4030 error. This is possible as the Oracle
messages are loaded on the client based on the client installs done