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: ORA-01555: snapshot too old: rollback segment number 24 with
 name "_SYSSMU24$" too small

Wittenmyer Joel - CO


This sounds similar to a known bug with ASSM tablespaces. The stats job
updates tables in SYSAUX. Those tables have indexes and up to if
an instance does massive DML (which the stats job does in our case.
Terabyte oltp with daily data loads and many schemas) on segments in an ASSM
tablespace that has indexes, the undo is unbelievable. In our case it
produces 10x the undo / redo it normally would. It can cause not only
ora-1555, but you can blow out the max extents (32767) for an undo segment.
The 'workaround' of coalescing the indexes prior to running such DML is only
minimally effective. The backport patch for previous versions in some cases
flat doesn't work (I know from experience.) The only sure fix is to upgrade
to, which I am told definitely fixes the issue, and which I am
preparing to do on several production instances even thought I HATE applying
the latest patchset (hornet's nest). Of course, if you are already on and are seeing this, please let me know!

-----Original Message-----
From: oracle-l-bounce@(protected)]
On Behalf Of Alex Gorbachev
Sent: Tuesday, June 27, 2006 2:52 PM
To: oracle-l@(protected)
Subject: Re: ORA-01555: snapshot too old: rollback segment number 24 with
name "_SYSSMU24$" too small

Duration 1151404820? That's like 36+ years... a bit odd, uh? :)

Anyway, ORA-1555 is often thrown regardless space availability in UNDO
tablespace. You can get it any time for read only transaction (or
single select) after it's running for retention_period time. Select
requires read consistent image of blocks and those are reconstructed
from UNDO info. UNDO info is kept for undo retention period. As soon
as you reach it - chances are you hit ORA-1555 on any more or less
often updatable table.

And yet another reason to delete this infamous job ASAP!

2006/6/27, arul kumar <arul76_2000@(protected)>:
> I have this recent error in alert log coming from the
> stats update job. Though the SQL is given partly, not
> able to find the EXACT database object that had
> problem. Any clue?
> ..
> ....
> Tue Jun 27 03:40:20 2006
> ORA-01555 caused by SQL statement below (Query
> Duration=1151404820 sec, SCN: 0x0849.81c92aa1):

Best regards,
Alex Gorbachev