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: tempspace usage

Greg Norris


> It seems that all of the problematic sessions are split between
> LOB_DATA and LOB_INDEX, with the former taking the majority of the
> space. I'm guessing this means that the application is using
> temporary LOBS, and not releasing them once they're no longer
> needed... I'll check with the developers.

That was it. The application was creating temporary LOBs with
duration set to SESSION, and not explicitly releasing them. Since
this particular app uses persistent DB connections, it just kept
creating more and more of the beasties until eventually the tempspace
was exhausted.

The developers have updated their code, and are testing the changes
now. If all goes well, the fix will be implemented sometime this

Thanx to everyone for your assistance... especially Steve Rospo, who
got me facing in what turned out to be the correct direction. :-)

"I'm too sexy for my code." - Awk Sed Fred.