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

Home -> Community -> Usenet -> c.d.o.server -> Re: Lock detection and resolution

Re: Lock detection and resolution

From: Vikas Agnihotri <onlyforposting_at_yahoo.com>
Date: 25 May 2001 06:18:20 -0700
Message-ID: <77e87b58.0105250518.5f3fcca9@posting.google.com>

Thomas Kyte <tkyte_at_us.oracle.com> wrote in message news:<tucrgtc0blq1sbindn85n13lpea5vcp3l4_at_4ax.com>...
>

[select ... for update nowait]

Thanks for the great explanation.

This is what I thought, but I have another question.

'select for update nowait' places a row-exclusive lock on the row, right? How can the session release this lock? Only by doing a commit/rollback? This is too drastic. Is there any other way?

The issue I have with the 'select for update nowait' is that it is too heavy-handed. i.e. it tries to check if a row is locked by trying to lock it itself! Seems a little odd.

Isnt there a way to determine if the row is "dirty" without attempting to lock it myself?

Or am I completely off the mark?

Thanks,
Vikas Received on Fri May 25 2001 - 08:18:20 CDT

Original text of this message

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