Links
Home
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
The good old ORA-01555 rollback too small

The good old ORA-01555 rollback too small

2005-02-09       - By Kline.Michael
Reply:     1     2     3     4  

ORA-01555 (See ORA-01555.ora-code.com): snapshot too old: rollback segment number 3 with name "RBS02"
too small


Production got one of these last night from two huge jobs trying to run
against a table in the range of 200M rows. They were reading this table
based on perhaps months and codes to build another table. So perhaps job
A was reading "base" to build "job_a_table" based on current month and a
set of codes, and job B was reading "base" to build "job_b_table" based
on a different set of criteria.



I would normally assume this would have been just fine.



If not, is there any "locking" that can be done to stop the ORA-01555 (See ORA-01555.ora-code.com)?



(I still suspect some where along the line, someone tried to update
while these jobs were running.)



This has been running fine in the past. There are some new jobs being
brought into production.



Oracle is 8.1.7.4 on HP-UX. Rollback capacity is in the vicinity of 32
GB and has never ran out yet.







Michael Kline
Database Administration
SunTrust Technology Center
1030 Wilmer Avenue
Richmond, Virginia  23227
Outside 804.261.9446
STNet 643.9446

Cell 804.744.1545
<mailto:michael.kline@(protected)> michael.kline@(protected)
************************************************
The information transmitted is intended solely
for the individual or entity to which it is  
addressed and may contain confidential and/or
privileged material. Any review, retransmission,
dissemination or other use of or taking action
in reliance upon this information by persons or
entities other than the intended recipient is
prohibited. If you have received this email in
error please contact the sender and delete the
material from any computer. [ST:A234]
************************************************


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