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: [Q] undo tablespace did not release space?? (less quoting)

Daniel Fink


The allocation algorithm in 9i is such that a 'full' tablespace
not necessarily a bad thing. When a transaction needs additional
undo space, it will acquire space from the existing undo
until then it will keep the undo entries around. IIRC, SMON will
periodically clean up the undo tablespace. The bottom line is to
worry about a full tablespace, only worry about 1555 errors.

As for the automatic v. manual (rollback) debate, at Hotsos a
solid source said that AUM is not recommended for high-volume
systems. As this is not the 'official' Oracle stance, I won't
names, but I respect this person's opinion and find myself in

In the meantime, I suggest you acquire the only guaranteed
AUM Management tool...a good bottle of Scotch!


Paul Drake wrote:

> > We have ORACLE 9ir2 running on LINUX server. I
> > check
> > Tablespace and found undo tablespace almost full for
> > long time. It did NOT release space. The undo
> > tablespace setup are undo_management=AUTO
> > undo_retention=900. Does anyone know why it don't
> > release space?
> >
> > Thanks.
> After attending Dan's presentation at RMOUG, I'm
> thinking of reverting to rollback segments for loading
> situations (if not entirely).
> Pd
Please see the official ORACLE-L FAQ: http://www.orafaq.com
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe' in the subject line.
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html