Path: newssvr20.news.prodigy.com!newsmst01.news.prodigy.com!prodigy.com!news.linkpendium.com!news-out.visi.com!petbe.visi.com!news1.optus.net.au!optus!newsfeeder.syd.optusnet.com.au!news.optusnet.com.au!not-for-mail From: "Howard J. Rogers" Newsgroups: comp.databases.oracle.server References: Subject: Re: ORA-01555; does update/select sequence matter? Date: Wed, 12 Nov 2003 10:27:06 +1100 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Lines: 35 Message-ID: <3fb1704b$0$20185$afc38c87@news.optusnet.com.au> NNTP-Posting-Host: 203.164.6.10 X-Trace: 1068593228 20185 203.164.6.10 Xref: newssvr20.news.prodigy.com comp.databases.oracle.server:247479 "John" wrote in message news:f2f59d82.0311111519.5c73b65@posting.google.com... > Hi group, > > Sanity check. > 1. There is no way to assign a rollback segment to a 'session', right? No. Only per transaction. > 2. It does not matter whether update or select comes first, ORA-01555 > can potentially happen, rihgt? Not sure what the question means. 1555s generally happen because an update/insert/delete over-writes the rollback that a select elsewhere is going to need to generate it's read-consistent image of the data. If the DML happened first (and was committed), and then the select was fired off, there'd be no problem (because the select would be able to read the modified blocks directly. So the situation only really arises because one select starts, and is still running when DML happens. But it's a bit difficult to draw tidy timelines like that when you have multi-user simultaneous access. Regards HJR > > Thanks. > > > John