Hello,
I've some serious deadlock problem on a 4 instances program.
Here is the log :
- SESSION ID:(9.62) 2002-07-14 22:23:40.137
DEADLOCK DETECTED
Current SQL statement for this session:
DELETE FROM ARO_APP_RIN ARO WHERE ARO.NSQ_T16 = :b1 AND ARO.NSQ_RIN = :b2
----- PL/SQL Call Stack -----
object line object
handle number name
98171684 146 package body PCO00.CDGGBSA4_EPURATION
98176a2c 2 anonymous block
The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or from issuing incorrect ad-hoc SQL. The following
information may aid in determining the deadlock:
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)------
---
Resource Name process session holds waits process session holds
waits
TM-0001c8b3-00000000 16 9 SX SSX 9 14 SX
SSX
TM-0001c8b3-00000000 9 14 SX SSX 16 9 SX
SSX
session 9: DID 0001-0010-00000002 session 14: DID 0001-0009-00000002
session 14: DID 0001-0009-00000002 session 9: DID 0001-0010-00000002
Rows waited on:
Session 14: no row
Session 9: no row
Initrans on ARO_APP_RIN is 16 since the creation of the table, and i'm sure
it's not a applicative lock.
So is the "Current SQL statement for this session:" is always the last
statement that lead to the deadlock ?
There are some trigger on ARO_APP_RIN, Is it possible that a statement in
the trigger lead to this deadlock (the trigger work on tables whith initrans
= 1)
Thanks for any help.
Ludo
--
Ludovic Cayen (Adventec)
Received on Mon Jul 22 2002 - 04:49:54 CDT