Re: wield ORA-01555 error???
From: David Fitzjarrell <oratune_at_yahoo.com>
Date: Wed, 17 Mar 2010 08:09:57 -0700 (PDT)
Message-ID: <753707.3103.qm_at_web65411.mail.ac4.yahoo.com>
Date: Wed, 17 Mar 2010 08:09:57 -0700 (PDT)
Message-ID: <753707.3103.qm_at_web65411.mail.ac4.yahoo.com>
Thanks for the example; it's been added to the blog post with, of course, my comments. :) David Fitzjarrell ________________________________ From: Jared Still <jkstill_at_gmail.com> To: oratune_at_yahoo.com Cc: mccdba1_at_yahoo.com; Oracle-L@freelists.org Sent: Tue, March 16, 2010 4:46:39 PM Subject: Re: wield ORA-01555 error??? On Tue, Mar 16, 2010 at 11:40 AM, David Fitzjarrell <oratune_at_yahoo.com> wrote: Please read here: > > >http://oratips-ddf.blogspot.com/2008/02/dreaded-ora-01555.html > One thing of interest that this blog brought back to mind: It is entirely possible to fetch across commits in a loop and issue updates on the rows fetched, without worrying about getting an ORA-1555. Here's an example from the docs: http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28370/static.htm#sthref829 Scroll down to the bit on "Fetching Across Commits" This may not be something you always want to do, but there are circumstances that require it. I've used it in production code where the circumstances did require it, though I didn't commit after every update. We did some testing to find what we thought an ideal number of updates before a commit was issued, and no, I no longer remember what that number was. Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist Oracle Blog: http://jkstill.blogspot.com Home Page: http://jaredstill.com
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Mar 17 2010 - 10:09:57 CDT