From: "Daniel A. Morgan" <dmorgan@exesolutions.com>
Newsgroups: comp.databases.oracle.tools
Subject: Re: Row Locks?
Date: Tue, 05 Jun 2001 23:15:42 -0700
Organization: EXE
Message-ID: <3B1DCA8E.31D45DCA@exesolutions.com>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
References: <3b1cea0d.62185107@client.ne.news.psi.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cache-Post-Path: yabetcha.drizzle.com!unknown@ava25.drizzle.com
X-Cache: nntpcache 2.4.0b2 (see http://www.nntpcache.org/)
X-Complaints-To: newsabuse@supernews.com
Lines: 27


Sunday Driver wrote:

> Hi
>
> If 2 users try to update the same row at the same time, the one that
> gets there first gets to save and the other gets an error about the
> row having been modified by another user, right?
>
> My (other) question is:
> Has anyone ever heard of Oracle leaving some kind of permanent lock on
> the row so that all users after that get the error msg about the row
> having been modified by another user?
>
> If not, why would all future users get the error when they try to
> modify these rows?
> TIA
> Bryn
> "In such cases as these,
>        a good memory is unpardonable."

In answer to your first question ... yes.

In answer to your second ... issue a commit. If one has been issued you
have an error condition and need to track it down.

Daniel A. Morgan