| Deadlock trace [message #167283] |
Wed, 12 April 2006 04:38 |
ozmartin
Messages: 7
Registered: March 2006
Location: MILANO
|
Junior Member |
|
|
Hi! I have a problem with the deadlock trace
I don' t understand Why the second session of the deadlock is not clear like the first one; I give an trace example :
*** SESSION ID:(365.48627) 2006-02-17 10:31:37.910
DEADLOCK DETECTED
Current SQL statement for this session:
UPDATE CL_KEYFON00T SET DES_LUNA = CLFU_ELIM_CHAR_SPEC(:B2) WHERE COD_PERS = :B1 AND FLG_QUDA = 'A'
----- PL/SQL Call Stack -----
object line object
handle number name
c0000002ed7829e0 51 XXXXX.CL_RECAPI00G
c0000002e0116e58 1351 package body XXXXX.TRPK_CANC_TRANSITO
c0000002e0116e58 594 package body XXXXX.TRPK_CANC_TRANSITO
c0000002e0116e58 712 package body XXXXXXX.TRPK_CANC_TRANS
c0000002e0116e58 60 package body XXXXX.x_CANC_TRAN
c0000002e98fa5e8 2588 package body xxxxx.xxxx_xxxxxxxx
c0000002f6297d90 11365 package body xxx.xxPK_PROP_PO@@@@@
c0000002f6297d90 11453 package body xxBPK_PROPOSTA_PO@@@@
c0000003824787a0 1 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
TX-00030025-0024c226 258 365 X 248 231 X
TX-0002001e-002d3a2c 248 231 X 258 365 X
session 365: DID 0001-0102-000000E1 session 231: DID 0001-00F8-000000A2
session 231: DID 0001-00F8-000000A2 session 365: DID 0001-0102-000000E1
Rows waited on:
Session 231: obj - rowid = 00006F89 - AAAG+JAAOAAHlIMAAu
(dictionary objn - 28553, file - 14, block - 1987084, slot - 46)
Session 365: obj - rowid = 00006FA4 - AAAG+kAAOAABITuABr
(dictionary objn - 28580, file - 14, block - 296174, slot - 107)
Information on the OTHER waiting sessions:
Session 231:
pid=248 serial=59732 audsid=39098532 user: 39/ZUREPAR
O/S info: user: root, term: unknown, ospid: , machine: itzufwp1
program: JDBC Thin Client
application name: JDBC Thin Client, hash value=0
Current SQL Statement:
UPDATE xxxxxx = NVL(:B3 ,SYSDATE) - 1 WHERE xxx = :B2 AND xxx = :B1 AND FIN_VLDT IS NULL
End of information on OTHER waiting sessions.
With the few information on OTHER waiting session it' s very difficult to find the statement in the user_source .
Thanks early 4 all ! 
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
