Home
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

Steve Rospo

2005-04-19

Replies:

A 10046 trace should show direct path reads/writes when the session starts
sorting/hashing to disk. Also check the SEGTYPE column to see if the
space is being used for sort, hash or temporary tables/indexes.

If the problem is the space doesn't disappear from V$SORT_USAGE across
multiple statements, I'd bet it was temp tables/indexes because a sort or
hash should disappear when the statement ends while the temp table
persists until the end of the transaction or session depending on how its
scope was declared. The join to V$SQLAREA as has been suggested won't
help in this case because the V$SORT_USAGE.SQLADDR doesn't point anywhere
since no single SQL statement "owns" it. I've never been able to
effectively been able to map such a row back to a particular temp
table/index just using the data in V$SORT_USAGE.

If there's only one statement and it keeps running and running, allocating
space the entire time, it's the culprit. There's lots of reasons for
this: Massive hash join, ORDER BY on a massive result set (like a
cartesian product), really big GROUP BY, etc.

S-

On Tue, 19 Apr 2005, Greg Norris wrote:

> 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.=20
> 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 8.1.7.4.0 (32-bit), running on Solaris 8.

--
Stephen Rospo     Principal Software Architect
Vallent Corporation (formerly Watchmark-Comnitel)
Stephen.Rospo@(protected)

This email may contain confidential information. If you received this in
error, please notify the sender immediately by return email and delete this
message and any attachments. Thank you.


--
http://www.freelists.org/webpage/oracle-l