Showing results for 
Search instead for 
Did you mean: 

ora-60 deadlock

Steve Bear_1
Frequent Advisor

ora-60 deadlock

dead lock

oracle (version 8.1.6) has generated a trace with deadlock ora-60.

trace output...

*** 2004-01-16 07:52:56.234
*** SESSION ID:(55.20) 2004-01-16 07:52:56.230
Current SQL statement for this session:
INSERT INTO itc.ttisfc001100 (t$pdno,t$cprj,t$mitm,t$opro,t$cwar,t$qrdr,t$qntl,t$qdlv,t$qrjc,t$qrjp,t$qtbf,t$qbfd,t$qtbi,t$qtri,t$prdt,t$prdp,t$dldt,t$dldp,t
revi,t$Refcntd,t$Refcntu) VALUES (:1,:2,:3,:4,:5,:6,:7,:8,:9,:10,:11,:12,:13,:14,:15,:16,:17,:18,:19,:20,:21,:22,:23,:24,:25,:26,:27,:28,:29,:30,:31,:32,:33,:
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-0007000e-0000dd1f 14 55 X 22 57 X
TX-00090031-0000dd75 22 57 X 14 55 S
session 55: DID 0001-000E-00000004 session 57: DID 0001-0016-00000005
session 57: DID 0001-0016-00000005 session 55: DID 0001-000E-00000004
Rows waited on:
Session 57: obj - rowid = 00072448 - AAByRIABgAAAK8DAAJ
Session 55: no row


Any suggestion ? what was the problem , why session-55 with "no rows"


Joseph Loo
Honored Contributor

Re: ora-60 deadlock


There is quite a bit of info on ora-60 and deadlock in Oracle Metalink 164661.1 and 62365.1.

see attachments for the above metalink documents.

what you do not see does not mean you should not believe
Jean-Luc Oudart
Honored Contributor

Re: ora-60 deadlock

As Oracle customer you should have access to Metalink.
Check the followings notes for explanation on deadlock :
<62365.1> What to do with "ORA-60 Deadlock Detected" Errors
<164661.1> Ora-60 And Deadlocks Most Common Causes

fiat lux
Volker Borowski
Honored Contributor

Re: ora-60 deadlock


Metalink has some stuff on it.

Here is the shortcut:
Change storage clause INITRANS (default 1) to a higher value (5-10) (For table and indexes). In most cases, this gives you a better chance that the deadlock does not occur.
If you only do INSERTS, it might be sufficiant just to alter table/index.

If you have (or will have) massive concurrent updates on this table as well, you need to reorganize the table, so that the already allocated blocks get new INITRANS-entries.

Hope this helps
Martin Roesicke
Occasional Visitor

Re: ora-60 deadlock


seems, that you are using BaaN.
Update your Oracle Version to min.,
newest Portingset and newest Standard Objects.
Thats a well know problem in some Baan Sessions. At least you could contact BGS.