Analyse deadLock Error log empty buffer event

  • Hi,

    I am using SQL server 2000 SP4 (Flag 1204 set at startup) on Windows Server 2003, when a deadlock occured I get 'No Event' in the input buffer :

    Just like that:

    2006-11-28 11:14:53.73 spid3 0

    2006-11-28 11:14:53.73 spid3 Wait-for graph 0

    2006-11-28 11:14:53.73 spid3 0

    2006-11-28 11:14:53.73 spid3 Node:1 0

    2006-11-28 11:14:53.73 spid3 TAB: 48:516912913 [] CleanCnt:2 Mode: IX Flags: 0x0 0

    2006-11-28 11:14:53.73 spid3 Grant List 0:: 0

    2006-11-28 11:14:53.73 spid3 Owner:0x1c1a5d60 Mode: IX Flg:0x0 Ref:1 Life:02000000 SPID:140 ECID:0 0

    2006-11-28 11:14:53.73 spid3 SPID: 140 ECID: 0 Statement Type: INSERT Line #: 1 0

    2006-11-28 11:14:53.73 spid3 Input Buf: No Event: 0

    2006-11-28 11:14:53.73 spid3 Requested By: 0

    2006-11-28 11:14:53.73 spid3 ResType:LockOwner Stype:'OR' Mode: X SPID:119 ECID:0 Ec: (0x727559E0) Value:0x5ae3c720 Cost: (0/2538) 0

    2006-11-28 11:14:53.73 spid3 0

    2006-11-28 11:14:53.73 spid3 Node:2 0

    2006-11-28 11:14:53.73 spid3 RID: 48:1:4561:54 CleanCnt:2 Mode: X Flags: 0x2 0

    2006-11-28 11:14:53.73 spid3 Grant List 1:: 0

    2006-11-28 11:14:53.73 spid3 Owner:0x1c6b0960 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:119 ECID:0 0

    2006-11-28 11:14:53.73 spid3 SPID: 119 ECID: 0 Statement Type: SELECT Line #: 131 0

    2006-11-28 11:14:53.73 spid3 Input Buf: No Event: 0

    2006-11-28 11:14:53.73 spid3 Requested By: 0

    2006-11-28 11:14:53.73 spid3 ResType:LockOwner Stype:'OR' Mode: S SPID:140 ECID:0 Ec: (0x7466B9E0) Value:0x1c1a5c60 Cost: (0/C4) 0

    2006-11-28 11:14:53.73 spid3 Victim Resource Owner: 0

    2006-11-28 11:14:53.73 spid3 ResType:LockOwner Stype:'OR' Mode: S SPID:140 ECID:0 Ec: (0x7466B9E0) Value:0x1c1a5c60 Cost: (0/C4) 0

     

    Can someone tells me what I have to do to get an event in the input Buffer ?


    Kindest Regards,

    egpotus DBA

  • I'm pretty sure you need another trace flag, either 1205 or 1206.

    When I last used trace flags to track deadlocks I used 1204,1205 and 3605 - you get a lot of stuff mind so I'd suggest you cycle your error log every day.

    [font="Comic Sans MS"]The GrumpyOldDBA[/font]
    www.grumpyolddba.co.uk
    http://sqlblogcasts.com/blogs/grumpyolddba/

  • flag have been added, it should work, thank you, I will keep you posted


    Kindest Regards,

    egpotus DBA

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply