Re: Oracle Auto Commit during transaction.
Date: Tue, 18 Mar 2008 10:21:35 -0700 (PDT)
On Mar 17, 7:55 pm, joel garry <joel-ga..._at_home.com> wrote:
> On Mar 16, 7:47 pm, PowerOne <salazar.wi..._at_gmail.com> wrote:
> > I need a massive update.
> > So the only way to avoid error and the update
> > is to increase the UNDO tablespace size
> > or update one by one record.
> > Thank you.
> But you said thousands. That's not generally very massive. How big
> is your undo, and how much are you using? What errors are you
> seeing? How exactly are you updating? Mark and David both have valid
> points, we need a lot more information even to convince us that undo
> is your issue. If you are only doing thousands, I suspect you would
> have concurrency issues if you are seeing problems. But you might be
> doing the fetch across commits mistake if you are getting ORA-1555.
> There are proper ways to commit every x records, but they require more
> work than most people will put out, and when it comes down to it, it
> is basically splitting up the logical unit of work into pieces.
> @home.com is bogus.http://www.popsci.com/how-it-works/article/2008-03/popsci-presents-ho...
To the database the transaction is a logical unit of work, but to the application one transaction may be several units of work. A logical unit of work is all the object changes that need to either all happen together or not happen at all. Multiple units of work can be grouped together and submitted as a single transaction or you can perform each unit as a transaction. From an application point of view performing the task as multiple transactions each of which is a complete logical unit of work may be a requirement for scalability.
IMHO -- Mark D Powell -- Received on Tue Mar 18 2008 - 12:21:35 CDT