Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> deadlock but 'no row' in trace...

deadlock but 'no row' in trace...

From: Jaret Lafoudravecmonhné <toto_at_toto.com>
Date: Thu, 23 May 2002 15:49:25 +0200
Message-ID: <acirh2$jqj$1@reader1.imaginet.fr>


Hello,

I've two program running in the same time, and it often fail in some deadlock problems. I'm sure that the 2 jobs doesn't run on the same rows of the same table.

This is an extract of the trc file :

DEADLOCK DETECTED
Current SQL statement for this session:
UPDATE D03_TAR_COL SET
NSQ_T01=:b1,MNT_PVT_D03=ROUND(:b2,4),MNT_PAC_D03=ROUND(:b3,4),MNT_MAR_D03=RO UND(:b4,4),PCT_MAR_D03=ROUND(:b5,2),DAP_D03=:b6,DMJ_TEC=:b7,UMJ_TEC=:b8,CVE_ TEC=CVE_TEC + 1 WHERE COF_NSQ_T16 = :b9 AND NSQ_OFR = :b10 AND NOR_COF = :b11 AND NSQ_T16 = :b12 AND NSQ_POF = :b13 ----- PL/SQL Call Stack -----
  object line object
  handle number name

984414ac       899  package body PCO00.CDB_D03_MAJ
9815f410         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
TX-000a001a-00000a58        16      25     X             19      24
S
TX-00080016-00000d09        19      24     X             16      25
S
session 25: DID 0001-0010-00000002 session 24: DID 0001-0013-00000002 session 24: DID 0001-0013-00000002 session 25: DID 0001-0010-00000002 Rows waited on:
Session 24: no row
Session 25: no row

Why 'no row' in the 2 last line ?

Ludovic Cayen Received on Thu May 23 2002 - 08:49:25 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US