Trc file
=====
*** 2008-05-15 11:41:23.555
*** SERVICE NAME:(SYS$USERS) 2008-05-15 11:41:23.555
*** SESSION ID:(318.14591) 2008-05-15 11:41:23.555
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-00010026-00000ad4 32 318 X 26 314
S
TX-0026001b-0000054b 26 314 X 32 318
S
session 318: DID 0001-0020-0000327D session 314: DID 0001-001A-00003B32
session 314: DID 0001-001A-00003B32 session 318: DID 0001-0020-0000327D
Rows waited on:
Session 314: obj - rowid = 0000B658 - AAALZYAAGAAAJA2AAA
(dictionary objn - 46680, file - 6, block - 36918, slot - 0)
Session 318: no row
Information on the OTHER waiting sessions:
Session 314:
pid=26 serial=42071 audsid=26514 user: 45/OMC_H1SERVER11
O/S info: user: axadmin, term: unknown, ospid: 1234, machine: m1server
program: JDBC Thin Client
application name: JDBC Thin Client, hash value=0
Current SQL Statement:
INSERT INTO LinkRelationTable VALUES ('110296','109977','10371','-1')
End of information on OTHER waiting sessions.
Current SQL statement for this session:
delete from fdnmappingtable where fdn like '0=#1#/14=#172.24.34.202#/17=#172.
24.34.202#%'
===================================================
Likley you have a design problem caused by multiple add-hoc queries
trying to insert records with the same key values ... in this case as
yet uncommitted.
If you need further help post the DDL for the table and all PK and
unique constraints/indexes.
--
Daniel A. Morgan
Oracle Ace Director & Instructor
University of Washington
damo...@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org