Re: Snapshot too old error

I believe this indicates that your rollback segments are too small-- the data that you selected is no longer available in your current rollback segments. I would *strongly* advise going this route.

I don't believe Oracle has a transaction isolation level which is so non-isolated that it would allow you to read a "next" value which wasn't there when you made the query. I can't imagine a scenario that you'd want to do something like this, but if you did, why not modify the query to select, say, 1000 rows at a time, process them, and then requery for the next 1000 rows. Of course, you may miss some rows or get others twice as rows get inserted, changed, and removed, but that seems to be acceptable to you.

At 08:43 PM 9/13/2002, Pillai, Rajesh wrote:
> I am running a pro*c program which has a cursor which fetches data
> from a table which is constantly being updated by front-end, so I am
> getting "snapshot too old error". My requirement is not to adhere to the
> consistency of the data. I am fine if the data that my program is reading
> is not consistent. How can I ask oracle to not to give me this "snapshot
> too old" error even when the data is consistent/inconsistent.

Justin Cave

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Justin Cave
  INET: jcave_at_cableone.net

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: ListGuru_at_fatcity.com (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).