Re: Detecting SELECT FOR UPDATE WAIT ... failures

Gentlemen,

Thank you for your suggestions.

At the moment

• the vendor won't instrument the code to write diagnostic information.
• audit_trail is set to NONE and we can't easily recycle the database.

I was hoping that I might be able to get something out of LogMiner. However, on my brief test run I could spot INSERT, UPDATES, DELETES (as expected), but not SELECT FOR UPDATE. I suspect (from previous problems) that overlapping SELECT FOR UPDATEs are the cause of my problem, so I need a technique that can detect these.

Stuart

--
http://www.freelists.org/webpage/oracle-l