INF: Information on DBCC 1204 (Deadlock) OutputLast reviewed: April 28, 1997Article ID: Q103855 |
The information in this article applies to:
- Microsoft SQL Server version 4.2 for OS/2 - Microsoft SQL Server version 4.2
SUMMARYIf a deadlock problem is encountered, it is often useful to use the DBCC 1204 trace flag to gather additional information. 1204 prints out the deadlock chains and victim.
MORE INFORMATIONAn example of a 1204 output is below: *** Deadlock detected - process 5 trying to wait on process 1 Deadlock chain --> LOCK REQUEST INITIATING DEADLOCK: LOGICAL: SH_PAGE at 0x1887551e lockid=6074 spid=5 dbid=6Process 1 waiting on Process 5 for resource: LOGICAL. Lock requested by spid 1: SH_PAGE at 0x1867151e lockid=4301 spid=1 dbid=6BLOCKED by spid 5 with the following lock: EX_PAGE Blocking at 0x256752c0 lockid=4301 spid=5 dbid=6 pstat=0x0100[ ] VICTIM: process 1;pstat 0x0100 [ ]; cputime=26 VICTIM: process 5;pstat 0x0100 [ ]; cputime=8 Process 5 was selected as victimYour server command (process id #5) was deadlocked with another process and has been chosen as deadlock victim. Re-run your command. (Msg 1205, Level 13, State 1). Caller is deadlock victim (5: 0x0100)We can extract the following information from this output:
|
Additional query words:
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |