topic ora-60 deadlock in Operating System - HP-UX

ora-60 deadlock

Steve Bear_1 — Fri, 16 Jan 2004 04:22:25 GMT

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
DEADLOCK DETECTED
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
$apdt,t$cmdt,t$cldt,t$efdt,t$prcd,t$rwko,t$rpsd,t$nsdl,t$copr,t$matc,t$oprc,t$cpla,t$mupr,t$dvpr,t$covn,t$roul,t$oprn,t$matl,t$matn,t$subn,t$chel,t$sawl,t$cut
l,t$recn,t$insn,t$osta,t$nnts,t$pnpt,t$runi,t$ncmp,t$bfep,t$bfhr,t$mmpo,t$mmno,t$qoor,t$oprp,t$qcmo,t$qrjo,t$opcp,t$opcy,t$oprj,t$clot,t$post,t$comp,t$txta,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,:
34,:35,:36,:37,:38,:39,:40,:41,:42,:43,:44,:45,:46,:47,:48,:49,:50,:51,:52,:53,:54,:55,:56,:57,:58,:59,:60,:61,:62,:63,:64,:65,:66)
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
===================================================
PROCESS STATE

-----------------

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

Thanks,

Re: ora-60 deadlock

Joseph Loo — Fri, 16 Jan 2004 04:40:42 GMT

hi,

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.

regards.

Re: ora-60 deadlock

Jean-Luc Oudart — Fri, 16 Jan 2004 04:43:42 GMT

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

rgds,
Jean-Luc

Re: ora-60 deadlock

Volker Borowski — Fri, 16 Jan 2004 14:55:13 GMT

Well,

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
Volker

Re: ora-60 deadlock

Martin Roesicke — Wed, 21 Jan 2004 05:09:28 GMT

Well,

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

Martin