Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: When to Commit?

Re: When to Commit?

From: Sybrand Bakker <postbus_at_sybrandb.demon.nl>
Date: Sat, 02 Jul 2005 23:51:34 +0200
Message-ID: <e03ec158p6sf9tr30ofk1evb7d2usf5lnl@4ax.com>


On 2 Jul 2005 14:22:07 -0700, "Mark D Powell" <Mark.Powell_at_eds.com> wrote:

>Where there are concurrent DML operations against a target table then
>holding a row lock for the duration of a long running update task may
>be very undesirable. It should be acceptable for a batch process to
>wait a few seconds for a row, but even a two second wait may be two
>long for an OLTP user. You have to balance the two competing needs.

Sure, long-running updates ---> outside office hours.

Your approach is the typical 'fighting symptoms approach' That said, there shouldn't be any intermittent commits, EVER. If you need intermittent commit, your design is wrong.

--
Sybrand Bakker, Senior Oracle DBA
Received on Sat Jul 02 2005 - 16:51:34 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US