Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

how do i get the root cause for dead lock and fix the same.

User_OCZ1TJun 12 2012 — edited Jun 13 2012
Hi i am using 10.2.0.4.0 version of oracle.

I got dead lock in my application, due to which it is causing severe issue. I got the trace file too for the dead lock period, its as below.

Note: i checked out the column DUE_DATE of table TASKS , but its(DUE_DATE) not referred by any other table. As because i was under impression that missing index on foreign key must be causing the issue.

So can you please help me out in this reference.
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /cust/oracle/product/10.2.0.4.0
System name:	SunOS
Node name:	m1878nwk1.cust.loudcloud.com
Release:	5.9
Version:	Generic_122300-60
Machine:	sun4u
Instance name: PXGN
Redo thread mounted by this instance: 1
Oracle process number: 31
Unix process pid: 817, image: oracle@m1878nwk1.cust.loudcloud.com

*** 2012-05-13 09:15:48.380
*** ACTION NAME:() 2012-05-13 09:15:48.357
*** MODULE NAME:(JDBC Thin Client) 2012-05-13 09:15:48.357
*** SERVICE NAME:(SYS$USERS) 2012-05-13 09:15:48.357
*** SESSION ID:(2669.11850) 2012-05-13 09:15:48.357
DEADLOCK DETECTED ( ORA-00060 )
[Transaction Deadlock]
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
TX-013a001e-0007c810        31    2669     X             80     409           X
TX-00570009-0013e398        80     409     X             31    2669           X
session 2669: DID 0001-001F-00003AFD	session 409: DID 0001-0050-00000B19
session 409: DID 0001-0050-00000B19	session 2669: DID 0001-001F-00003AFD
Rows waited on:
Session 409: obj - rowid = 000328BB - AAAyi7AP4AAAyNQACI
  (dictionary objn - 207035, file - 1016, block - 205648, slot - 136)
Session 2669: obj - rowid = 000328BB - AAAyi7AP4AAAyNYAAC
  (dictionary objn - 207035, file - 1016, block - 205656, slot - 2)
Information on the OTHER waiting sessions:
Session 409:
  pid=80 serial=54868 audsid=1104473498 user: 36/XIGNCMN
  O/S info: user: weblogic, term: unknown, ospid: 1234, machine: m1868nwk1
            program: JDBC Thin Client
  application name: JDBC Thin Client, hash value=2546894660
  Current SQL Statement:
  UPDATE TASKS SET DUE_DATE=:1  WHERE  (  (TASK_PK = :2))
End of information on OTHER waiting sessions.
Current SQL statement for this session:
UPDATE TASKS SET DUE_DATE=:1  WHERE  (  (TASK_PK = :2))
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jul 11 2012
Added on Jun 12 2012
8 comments
1,703 views