On Mon, 27 May 2002, Nirmal Kumar Muthu Kumaran wrote: > Increase rollback segment size for this transaction and make sure > that the transaction will use the huge rollback segment
I don't think that solution is correct. This is a common misconception about "snapshot too old." Assigning your long-running select to a giant rollback segment will not help solve the problem. Here a short article on this misconception: http://www.speakeasy.org/~jwilton/oracle/snapshot-too-old.html I suspect the original poster is encountering "snapshot too old" as a result of block cleanouts. See the following article for more information: http://home.clara.net/dwotton/dba/snapshot2.htm -- Jeremiah Wilton http://www.speakeasy.net/~jwilton > > -----Original Message----- > > From: Andrey Bronfin [SMTP:[EMAIL PROTECTED]] > > > > There is something strange going on in my production DB. > > There is a program that reads fom 2 huge tables (A and B - select only) > > and > > writes a fraction of records into some third table (let's call it C - > > inserts only). > > Now , NO ONE carries a DML agains A or B . > > But occasionally i get the Ora-1555 - "snapshot too old" error during the > > run of the aforementioned program. -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Jeremiah Wilton INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
