Re: Detecting SELECT FOR UPDATE WAIT ... failures

is it possible to add something like this to the code...

when others then

    select stuff you need

       from v$view you need

log error message, etc... to a table
end;

can you get the vendor to add this change?

• Original message -------------- From: "Stuart Clowes" <stuart.clowes_at_gmail.com>

List,

We have a packaged app. One of our processes is issuing 'SELECT X FROM TABLE_Y WHERE A=:1 FOR UPDATE WAIT 10' (names changed to protect the vendor....). .

This process is periodically having problems because the 'SELECT FOR UPDATE' is timing out. This happens a few times a day, at unpredictable times. (Yes, I know the code should cope gracefully with this......... but it doesn't).

I've been asked - what other process is holding the lock that this process is failing to get?

The vendor is saying that they can't spot the conflicting DML in their code. A trace file doesn't seems to help. I can't spot 'SELECT FOR UPDATE' in Logminer output.

Do you have any thoughts on how I can approach this, aside from querying the lock views all day?

Stuart
--

http://www.freelists.org/webpage/oracle-l Received on Wed Jun 21 2006 - 12:09:10 CDT