Surely if you have the means to change the SELECT FOR UPDATE statements you
can take out the for update in most/all cases? If you can't change the
statements then surely there's no benefit in seeking alternatives.
On 12 Apr 2016 12:33, "walid kaakati" <dmarc-noreply@xxxxxxxxxxxxx> wrote:
Hallo List,
I working on an application that generates SQL Statements with *SELECT
FOR UPDATE* clause, these Statements cause a lock on the select rows and
hence blocking other sessions,sometimes the lock stay for half an hour
according to the selected data.
From analzying the Locks ,i found the locking due to Logical Errors in the
development of the applciation .
My question from PL-SQL viewpoint is their an alternative for this
mechanisem that requires a lock on the Selected rows for Update ? any
recommedation to minimize this Locking ?
my (Database is 10g ).
Best Wishes,
