Re: How to get the statment sql that caused the lock
From: Mladen Gogala <gogala.mladen_at_gmail.com>
Date: Mon, 29 Oct 2018 18:21:42 -0400
Message-ID: <eb9572f2-fe89-94d6-7637-f0e0d779ccb3_at_gmail.com>
Date: Mon, 29 Oct 2018 18:21:42 -0400
Message-ID: <eb9572f2-fe89-94d6-7637-f0e0d779ccb3_at_gmail.com>
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-lReceived on Mon Oct 29 2018 - 23:21:42 CET