Application DEADLOCKS [message #312799] |
Wed, 09 April 2008 15:40 |
|
BlackSwan
Messages: 26766 Registered: January 2009 Location: SoCal
|
Senior Member |
|
|
The application is throwing ORA-00060 & I need to assist with resolving this issue.
The application folks swear that there is "NO WAY" their application will have two different sessions trying to delete the same row.
If/how can I extract the value of the bind variables involved with the 2 DELETE statements below?
*** 2008-04-09 10:55:44.298
*** SERVICE NAME:(SYS$USERS) 2008-04-09 10:55:44.298
*** SESSION ID:(439.31952) 2008-04-09 10:55:44.298
DEADLOCK DETECTED
[Transaction Deadlock]
Current SQL statement for this session:
DELETE FROM tblStatusProfile WHERE StatusProfileID=:1
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-0000c9c5-00000000 196 439 SX SSX 66 313 SX SSX
TM-0000c9c5-00000000 66 313 SX SSX 196 439 SX SSX
session 439: DID 0001-00C4-00001E29 session 313: DID 0001-0042-0000000A
session 313: DID 0001-0042-0000000A session 439: DID 0001-00C4-00001E29
Rows waited on:
Session 313: no row
Session 439: no row
Information on the OTHER waiting sessions:
Session 313:
pid=66 serial=17591 audsid=1171907 user: 55/INLOGIC
O/S info: user: , term: , ospid: 1234, machine: gs12dn
program:
Current SQL Statement:
DELETE FROM tblStatusProfile WHERE StatusProfileID=:1
End of information on OTHER waiting sessions.
===================================================
Any other ideas or suggestions on how to better understand what is or is not happening would be greatly appreciated.
TIA!
|
|
|
|
|
|
|
|