60: ORA-00060: deadlock detected while waiting for resource

[srujan_reddy]

Hi All

*** 2009-09-14 10:13:25.249
*** SESSION ID12.38166) 2009-09-14 10:13:25.222
DEADLOCK DETECTED
Current SQL statement for this session:
DELETE FROM CR_TEL_CPE_CUSTOMER WHERE TEL_CNX_ID = :b1 AND CUSTOMER_ID = :b2 AND LOCATION_FLAT_ID = :b3

----- PL/SQL Call Stack -----
object line object
handle number name
95da8954 6620 package body OSSNI.CRM
963e735c 1 anonymous block
958ab844 1118 package body SYS.DBMS_SYS_SQL
94cf146c 316 package body SYS.DBMS_SQL
94ab1f8c 1676 package body OSSNI_PE.CRM
954c0de8 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-00030f55-00000000 32 12 SX SSX 34 53 SX SSX
TM-00030f55-00000000 34 53 SX SSX 32 12 SX SSX
session 12: DID 0001-0020-00000002 session 53: DID 0001-0022-00000002
session 53: DID 0001-0022-00000002 session 12: DID 0001-0020-00000002
Rows waited on:
Session 53: no row
Session 12: no row

this is the error am getting
May i know wat kind of dead lock error is this?? and how to resolve it??
when i was googling i found that this error is due to Unindexed foriegn keys
but the table which was shown in the trace logs has indexed foriegn key

can anyone please help me regarding this

[giteshtrivedi]

Hi,

Use "select for update" for get rid of ORA-60 Deadlock errors.