Deadlock encounterd

suvidha

Hi, please help me understand this ERRORLOG:

Deadlock encountered .... Printing deadlock information
2008-12-26 10:28:52.17 spid1
2008-12-26 10:28:52.17 spid1 Wait-for graph
2008-12-26 10:28:52.17 spid1
2008-12-26 10:28:52.17 spid1 Node:1
2008-12-26 10:28:52.17 spid1 KEY: 7:177904201:1 (ffffffffffff) CleanCnt:2 Mode: Range-S-U Flags: 0x0
2008-12-26 10:28:52.17 spid1 Grant List 1::
2008-12-26 10:28:52.17 spid1 Owner:0x3b6b6aa0 Mode: Range-S-U Flg:0x0 Ref:0 Life:02000000 SPID:152 ECID:0
2008-12-26 10:28:52.17 spid1 SPID: 152 ECID: 0 Statement Type: EXECUTE Line #: 1
2008-12-26 10:28:52.17 spid1 Input Buf: RPC Event: sp_cursoropen;1
2008-12-26 10:28:52.17 spid1 Requested By:
2008-12-26 10:28:52.17 spid1 ResType:LockOwner Stype:'OR' Mode: Range-S-U SPID:148 ECID:0 Ec:(0x48FBF568) Value:0x65383960 Cost:(0/DA88)

2008-12-26 10:28:52.17 spid1
2008-12-26 10:28:52.17 spid1 Node:2
2008-12-26 10:28:52.17 spid1 KEY: 7:1361192395:1 (ffffffffffff) CleanCnt:2 Mode: Range-S-U Flags: 0x0
2008-12-26 10:28:52.17 spid1 Grant List 2::
2008-12-26 10:28:52.17 spid1 Owner:0x29f1e880 Mode: Range-S-U Flg:0x0 Ref:0 Life:02000000 SPID:148 ECID:0
2008-12-26 10:28:52.17 spid1 SPID: 148 ECID: 0 Statement Type: EXECUTE Line #: 1
2008-12-26 10:28:52.17 spid1 Input Buf: RPC Event: sp_cursoropen;1
2008-12-26 10:28:52.17 spid1 Requested By:
2008-12-26 10:28:52.17 spid1 ResType:LockOwner Stype:'OR' Mode: Range-S-U SPID:152 ECID:0 Ec:(0x370CB560) Value:0x2d5daf20 Cost:(0/251C)
2008-12-26 10:28:52.17 spid1 Victim Resource Owner:
2008-12-26 10:28:52.17 spid1 ResType:LockOwner Stype:'OR' Mode: Range-S-U SPID:152 ECID:0 Ec:(0x370CB560) Value:0x2d5daf20 Cost:(0/251C)

Here in node1 Object name=Value entry
and in nde2 object name=G/L Entry

This is all i understood!!! :oops:

stryk

Hi!
Well, there is little more, but not much ...
For example:

KEY: 7:177904201:1

KEY = Granularity of Lock
7 = Database ID
177904201 = Object ID (I guess you knew that)
1 = INdex ID (probably Clustered Index)

Input Buf: RPC Event: sp_cursoropen;1

sp_cursoropen = (Probably) in NAV a FIND('-'), FIND('+') or FINDSET was fired

SPID: 148
148 = the procress ID which was involved in the deadlock (unfortunately this does not tell you anything about the user behind that SPIT at THIS time)

But anyway, it's not telling a lot ... ](*,)

Maybe you want to check out this to find a more convenient method to investigare deadlocks: http://dynamicsuser.net/blogs/stryk/archive/2008/11/03/blocks-amp-deadlocks-in-nav-with-sql-server.aspx

Regards,
Jörg