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: Strange snapshot too old during a select statement

Richard Foote

2004-03-11

Replies:
Strange snapshot too old during a select statementHi Philippe,

Ummm, I must be missing something here ?

Snapshot too old errors occur because Oracle can't reconstruct a consistent
image of a block for the purposes of a consistent read.

And when do you generally require a consistent read ? During a select ...

And when are you likely to hit a snapshot too old ? During a long running
select as Oracle needs to reconstruct all blocks back to the time the query
started and the likelihood of such being possible diminishes over time.

You've described the classic scenario when ORA-01555s occur.

I think the Oracle Support person who said it's not possible since this was
only a select statement is smoking some seriously dangerous substances ;)

Cheers

Richard


----- Original Message -----
From: NGUYEN Philippe (Cetelem)
To: 'oracle-l@(protected)'
Sent: Thursday, March 11, 2004 6:46 PM
Subject: Strange snapshot too old during a select statement


Hi list!
we encounter a very strange "ORA-01555 : snapshot too old :rollback segment
number 3 with name "_SYSSMU3$" too small"
This is a very long query
With a query that only make a select statement.
We have open a TAR with Oracle Support but they say that it's not possible
since this only a "select" statement ?!!
Any idea ?
TIA
Philippe


----------------------------------------------------------------
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
-----------------------------------------------------------------