RE: How to get the statment sql that caused the lock

Well, not exactly. I’m not talking about multiple DB servers or multiple databases. I’m talking about clients to middle tiers tossing and executing code at the database one statement at a time, starting a transaction that is not even distributed causing a lock of indeterminate duration.  

I’m not arguing about when locks do to two phase commit can be stranded, which is another real case, but where at least the developer IS likely to be in control of the situation explicitly.      

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Mladen Gogala Sent: Monday, October 29, 2018 6:22 PM
To: Mark W. Farnham; 'Eriovaldo Andrietta'; neil_chandler_at_hotmail.com Cc: 'ORACLE-L'
Subject: Re: How to get the statment sql that caused the lock  

YESSS! That is precisely the scenario I described as "distributed queries causing locks".

On 10/29/18 11:06 AM, Mark W. Farnham wrote:

When a transaction is interrupted by any sort of a network hiccup (most insidiously between a client machine and the middle tier with no loss of connectivity between a middle tier and the database apparent unless a timeout is configured) then the locks on the statements of the transaction thus far in play can be held for a very long time.  

--

Mladen Gogala
Database Consultant
Tel: (347) 321-1217

--

http://www.freelists.org/webpage/oracle-l Received on Tue Oct 30 2018 - 15:30:04 CET