求何位大侠帮忙分析下死锁日志
求哪位大侠帮忙分析下死锁日志
通过 DBCC TRACEON (3605,1204,1222,-1)
抓到了死锁日志，日志附在下面，我不太明白是，先UPDATE再INSERT，怎么会是有了X锁，再请求RangeS-S锁呢？
具体日志如下：
59:50. spid5s Deadlock encountered .... Printing deadlock information
59:50. spid5s Wait-for graph
59:50. spid5s NULL
59:50. spid5s Node:1
59:50. spid5s KEY: 6:72057594065715200 (8500ea663c04) CleanCnt:2 Mode:RangeS-U Flags: 0x1
59:50. spid5s Grant List 2:
59:50. spid5s Owner:0x00000000077E4AC0 Mode: RangeS-U Flg:0x40 Ref:0 Life:00000001 SPID:66 ECID:0 XactLockInfo: 0x00000007D3EEE3F0
59:50. spid5s SPID: 66 ECID: 0 Statement Type: UPDATE Line #: 92
59:50. spid5s Input Buf: RPC Event: Proc [Database Id = 6 Object Id = 1463676262]
59:50. spid5s Requested by:
59:50. spid5s ResType:LockOwner Stype:'OR'Xdes:0x0000000080092570 Mode: RangeS-U SPID:57 BatchID:0 ECID:0 TaskProxy:(0x000000022CE2C538) Value:0x785b500 Cost:(0/480)
59:50. spid5s NULL
59:50. spid5s Node:2
59:50. spid5s KEY: 6:72057594048806912 (6200429172ae) CleanCnt:2 Mode:X Flags: 0x1
59:50. spid5s Grant List 2:
59:50. spid5s Owner:0x0000000006D05CC0 Mode: X Flg:0x40 Ref:0 Life:02000001 SPID:57 ECID:0 XactLockInfo: 0x00000000800925B0
59:50. spid5s SPID: 57 ECID: 0 Statement Type: UPDATE Line #: 57
59:50. spid5s Input Buf: RPC Event: Proc [Database Id = 6 Object Id = 1463676262]
59:50. spid5s Requested by:
59:50. spid5s ResType:LockOwner Stype:'OR'Xdes:0x00000007D3EEE3B0 Mode: RangeS-S SPID:66 BatchID:0 ECID:0 TaskProxy:(0x00000006C426A538) Value:0x6ba2700 Cost:(0/1236)
59:50. spid5s NULL
59:50. spid5s Victim Resource Owner:
59:50. spid5s ResType:LockOwner Stype:'OR'Xdes:0x0000000080092570 Mode: RangeS-U SPID:57 BatchID:0 ECID:0 TaskProxy:(0x000000022CE2C538) Value:0x785b500 Cost:(0/480)
59:50. spid24s deadlock-list
59:50. spid24s deadlock victim=process6463b88
59:50. spid24s process-list
59:50. spid24s process id=process6463b88 taskpriority=0 logused=480 waitresource=KEY: 6:72057594065715200 (8500ea663c04)
通过 DBCC TRACEON (3605,1204,1222,-1)
抓到了死锁日志，日志附在下面，我不太明白是，先UPDATE再INSERT，怎么会是有了X锁，再请求RangeS-S锁呢？
具体日志如下：
59:50. spid5s Deadlock encountered .... Printing deadlock information
59:50. spid5s Wait-for graph
59:50. spid5s NULL
59:50. spid5s Node:1
59:50. spid5s KEY: 6:72057594065715200 (8500ea663c04) CleanCnt:2 Mode:RangeS-U Flags: 0x1
59:50. spid5s Grant List 2:
59:50. spid5s Owner:0x00000000077E4AC0 Mode: RangeS-U Flg:0x40 Ref:0 Life:00000001 SPID:66 ECID:0 XactLockInfo: 0x00000007D3EEE3F0
59:50. spid5s SPID: 66 ECID: 0 Statement Type: UPDATE Line #: 92
59:50. spid5s Input Buf: RPC Event: Proc [Database Id = 6 Object Id = 1463676262]
59:50. spid5s Requested by:
59:50. spid5s ResType:LockOwner Stype:'OR'Xdes:0x0000000080092570 Mode: RangeS-U SPID:57 BatchID:0 ECID:0 TaskProxy:(0x000000022CE2C538) Value:0x785b500 Cost:(0/480)
59:50. spid5s NULL
59:50. spid5s Node:2
59:50. spid5s KEY: 6:72057594048806912 (6200429172ae) CleanCnt:2 Mode:X Flags: 0x1
59:50. spid5s Grant List 2:
59:50. spid5s Owner:0x0000000006D05CC0 Mode: X Flg:0x40 Ref:0 Life:02000001 SPID:57 ECID:0 XactLockInfo: 0x00000000800925B0
59:50. spid5s SPID: 57 ECID: 0 Statement Type: UPDATE Line #: 57
59:50. spid5s Input Buf: RPC Event: Proc [Database Id = 6 Object Id = 1463676262]
59:50. spid5s Requested by:
59:50. spid5s ResType:LockOwner Stype:'OR'Xdes:0x00000007D3EEE3B0 Mode: RangeS-S SPID:66 BatchID:0 ECID:0 TaskProxy:(0x00000006C426A538) Value:0x6ba2700 Cost:(0/1236)
59:50. spid5s NULL
59:50. spid5s Victim Resource Owner:
59:50. spid5s ResType:LockOwner Stype:'OR'Xdes:0x0000000080092570 Mode: RangeS-U SPID:57 BatchID:0 ECID:0 TaskProxy:(0x000000022CE2C538) Value:0x785b500 Cost:(0/480)
59:50. spid24s deadlock-list
59:50. spid24s deadlock victim=process6463b88
59:50. spid24s process-list
59:50. spid24s process id=process6463b88 taskpriority=0 logused=480 waitresource=KEY: 6:72057594065715200 (8500ea663c04)