Skip to Content
0
Former Member
May 14, 2008 at 09:35 AM

Deadlock detected as ORA-00060

384 Views

hi,

deadlock detected in DEV box with below warnings :

BR0976W Database message alert - level: WARNING, line: 38869, time: 2008-05-12 00.31.38, message:

ORA-00060: Deadlock detected. More info in file /oracle/DV1/saptrace/usertrace/dv1_ora_1187980.trc .

BR0280I BRCONNECT time stamp: 2008-05-12 06.20.37

I checked at OS level also. I found following message :

DEADLOCK DETECTED ( ORA-00060 )

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-0012000c-00003699

21

37

X

19

25

X

TX-0007001c-000035f9

19

25

X

21

37

X

session 37: DID 0001-0015-0000000A

session 25: DID 0001-0013-00000016

session 25: DID 0001-0013-00000016

session 37: DID 0001-0015-0000000A

Rows waited on:

Session 25: obj - rowid = 0000489B - AAAEibAAfAAAAUTAAE

(dictionary objn - 18587, file - 31, block - 1299, slot - 4)

Session 37: obj - rowid = 0000489B - AAAEibAAfAAAAUPAAa

(dictionary objn - 18587, file - 31, block - 1295, slot - 26)

Information on the OTHER waiting sessions:

can anybody help me out for exact solution..

regards

Anju