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


Billy Verreynne (JW)



Busy hunting Metalink for information, but maybe someone here can
point me to likely causes to investigate.

I get ORA-06508 "PL/SQL: could not find program unit being called".
Not an unusual error and the cause is very obvious. Or so I thought
till now.

What is unusual is that the unit being called exists. The caller is
the owner of that procedure.

The caller calls a range of these procedures.. and everything works
fine until this single unit (proc) is called. The caller runs via
DBMS_JOB. The proc being complained about is not invalid. Dynamic SQL
is not being used. The same DBMS_JOB has been running fine (every hour
on the hour) and the error is intermittant. It's not an issue of
another user interfering (I have the RAC to myself). Scope should not
play a role (no ALTER SESSION to set current_schema). No manual reset
of package states. Just plain vanilla code that does INSERT..SELECTs -
nothing out of the ordinary. Nothing that could cause the proc in
question to be invalidated (which should give a different error?) or
actually being drop and re-created.

Directly after the error and the DBMS_JOB failing, I can run the
actual proc being complained about - no errors. I can run the actual
caller proc (the one scheduled via DBMS_JOB) that calls the range of
procedures to perform the hourly processing - no errors. Very weird..

Platform details:
12 node Enterprise RAC running on Red Hat ES3.


This e-mail and its contents are subject to the Telkom SA Limited
e-mail legal notice available at