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

Hollis, Les


Are you sure that the transactions are still holding the space?

Temp tablespace segments do NOT de-allocate when a session quits using
it. It will remain allocated so the next user to need temp space does
not have to go through the space allocation......

PMON will de-allocate the segments on the next instance startup.

-----Original Message-----
From: oracle-l-bounce@(protected)
Sent: Tuesday, April 19, 2005 2:55 PM
Subject: tempspace usage

Is there a way to determine (or trace) which individual statements are
causing tempspace to be allocated to a session? I've got a databases
where half a dozen sessions seem to gradually allocate more and more
tempspace (as measured by v$sort_usage), and then never release it.=3D20
Eventually they acquire almost all of the available space, which of
course causes a flurry of ORA-1652 errors from other sessions.

At the moment, I'm examining a trace from one of these sessions. So
far, I don't see anything which could cause this behaviour... a few
inserts, some relatively simple selects, nothing particularly complex.
Any suggestions on how to troubleshoot this sort of issue?

The DB in question is Oracle (32-bit), running on Solaris 8.