Deadlock problem

Hello,
I am battling various deadlocks on our system and have the trace flag
1204 turned on so that I get information on what was involved in the
deadlock. Today, however, I saw something that I've never seen before
(see below). What does 'Port' mean? How can I figure out what exactly
was involved in the deadlock.
Node:2
Port: 0x42c30a80 Xid Slot: 0, EC: 0x668115a0, ECID: 0 (Coordinator),
Exchange Wait Type :e_etypeCXPacket
Coordinator: EC = 0x668115a0, SPID: 98, ECID: 0, Not Blocking
Consumer List::
Consumer: Xid Slot: 0, EC = 0x668115a0, SPID: 98, ECID: 0, Not Blocking
Producer List::
Producer: Xid Slot: 1, EC = 0x3f25c0c0, SPID: 98, ECID: 3, Blocking
Producer: Xid Slot: 2, EC = 0x47b0e0c0, SPID: 98, ECID: 1, Blocking
Producer: Xid Slot: 3, EC = 0x3d1280c0, SPID: 98, ECID: 2, Blocking
Producer: Xid Slot: 4, EC = 0x3f8d40c0, SPID: 98, ECID: 4, Blocking
Thanks.
Just curious how to read it outside the port as well ? ;) Would be nice to
know what that translates to .
"Frank Rizzo" <none@.none.com> wrote in message
news:emogpuFKGHA.1320@.TK2MSFTNGP15.phx.gbl...
> Hello,
> I am battling various deadlocks on our system and have the trace flag 1204
> turned on so that I get information on what was involved in the deadlock.
> Today, however, I saw something that I've never seen before (see below).
> What does 'Port' mean? How can I figure out what exactly was involved in
> the deadlock.
>
>
> Node:2
> Port: 0x42c30a80 Xid Slot: 0, EC: 0x668115a0, ECID: 0 (Coordinator),
> Exchange Wait Type :e_etypeCXPacket
> Coordinator: EC = 0x668115a0, SPID: 98, ECID: 0, Not Blocking
> Consumer List::
> Consumer: Xid Slot: 0, EC = 0x668115a0, SPID: 98, ECID: 0, Not Blocking
> Producer List::
> Producer: Xid Slot: 1, EC = 0x3f25c0c0, SPID: 98, ECID: 3, Blocking
> Producer: Xid Slot: 2, EC = 0x47b0e0c0, SPID: 98, ECID: 1, Blocking
> Producer: Xid Slot: 3, EC = 0x3d1280c0, SPID: 98, ECID: 2, Blocking
> Producer: Xid Slot: 4, EC = 0x3f8d40c0, SPID: 98, ECID: 4, Blocking
> Thanks.

Deadlock problem

Hello,
I am battling various deadlocks on our system and have the trace flag
1204 turned on so that I get information on what was involved in the
deadlock. Today, however, I saw something that I've never seen before
(see below). What does 'Port' mean? How can I figure out what exactly
was involved in the deadlock.
Node:2
Port: 0x42c30a80 Xid Slot: 0, EC: 0x668115a0, ECID: 0 (Coordinator),
Exchange Wait Type :e_etypeCXPacket
Coordinator: EC = 0x668115a0, SPID: 98, ECID: 0, Not Blocking
Consumer List::
Consumer: Xid Slot: 0, EC = 0x668115a0, SPID: 98, ECID: 0, Not Blocking
Producer List::
Producer: Xid Slot: 1, EC = 0x3f25c0c0, SPID: 98, ECID: 3, Blocking
Producer: Xid Slot: 2, EC = 0x47b0e0c0, SPID: 98, ECID: 1, Blocking
Producer: Xid Slot: 3, EC = 0x3d1280c0, SPID: 98, ECID: 2, Blocking
Producer: Xid Slot: 4, EC = 0x3f8d40c0, SPID: 98, ECID: 4, Blocking
Thanks.Just curious how to read it outside the port as well ? ;) Would be nice to
know what that translates to .
"Frank Rizzo" <none@.none.com> wrote in message
news:emogpuFKGHA.1320@.TK2MSFTNGP15.phx.gbl...
> Hello,
> I am battling various deadlocks on our system and have the trace flag 1204
> turned on so that I get information on what was involved in the deadlock.
> Today, however, I saw something that I've never seen before (see below).
> What does 'Port' mean? How can I figure out what exactly was involved in
> the deadlock.
>
>
> Node:2
> Port: 0x42c30a80 Xid Slot: 0, EC: 0x668115a0, ECID: 0 (Coordinator),
> Exchange Wait Type :e_etypeCXPacket
> Coordinator: EC = 0x668115a0, SPID: 98, ECID: 0, Not Blocking
> Consumer List::
> Consumer: Xid Slot: 0, EC = 0x668115a0, SPID: 98, ECID: 0, Not Blocking
> Producer List::
> Producer: Xid Slot: 1, EC = 0x3f25c0c0, SPID: 98, ECID: 3, Blocking
> Producer: Xid Slot: 2, EC = 0x47b0e0c0, SPID: 98, ECID: 1, Blocking
> Producer: Xid Slot: 3, EC = 0x3d1280c0, SPID: 98, ECID: 2, Blocking
> Producer: Xid Slot: 4, EC = 0x3f8d40c0, SPID: 98, ECID: 4, Blocking
> Thanks.

Deadlock problem

Hello,
I am battling various deadlocks on our system and have the trace flag
1204 turned on so that I get information on what was involved in the
deadlock. Today, however, I saw something that I've never seen before
(see below). What does 'Port' mean? How can I figure out what exactly
was involved in the deadlock.
Node:2
Port: 0x42c30a80 Xid Slot: 0, EC: 0x668115a0, ECID: 0 (Coordinator),
Exchange Wait Type :e_etypeCXPacket
Coordinator: EC = 0x668115a0, SPID: 98, ECID: 0, Not Blocking
Consumer List::
Consumer: Xid Slot: 0, EC = 0x668115a0, SPID: 98, ECID: 0, Not Blocking
Producer List::
Producer: Xid Slot: 1, EC = 0x3f25c0c0, SPID: 98, ECID: 3, Blocking
Producer: Xid Slot: 2, EC = 0x47b0e0c0, SPID: 98, ECID: 1, Blocking
Producer: Xid Slot: 3, EC = 0x3d1280c0, SPID: 98, ECID: 2, Blocking
Producer: Xid Slot: 4, EC = 0x3f8d40c0, SPID: 98, ECID: 4, Blocking
Thanks.Just curious how to read it outside the port as well ? ;) Would be nice to
know what that translates to .
"Frank Rizzo" <none@.none.com> wrote in message
news:emogpuFKGHA.1320@.TK2MSFTNGP15.phx.gbl...
> Hello,
> I am battling various deadlocks on our system and have the trace flag 1204
> turned on so that I get information on what was involved in the deadlock.
> Today, however, I saw something that I've never seen before (see below).
> What does 'Port' mean? How can I figure out what exactly was involved in
> the deadlock.
>
>
> Node:2
> Port: 0x42c30a80 Xid Slot: 0, EC: 0x668115a0, ECID: 0 (Coordinator),
> Exchange Wait Type :e_etypeCXPacket
> Coordinator: EC = 0x668115a0, SPID: 98, ECID: 0, Not Blocking
> Consumer List::
> Consumer: Xid Slot: 0, EC = 0x668115a0, SPID: 98, ECID: 0, Not Blocking
> Producer List::
> Producer: Xid Slot: 1, EC = 0x3f25c0c0, SPID: 98, ECID: 3, Blocking
> Producer: Xid Slot: 2, EC = 0x47b0e0c0, SPID: 98, ECID: 1, Blocking
> Producer: Xid Slot: 3, EC = 0x3d1280c0, SPID: 98, ECID: 2, Blocking
> Producer: Xid Slot: 4, EC = 0x3f8d40c0, SPID: 98, ECID: 4, Blocking
> Thanks.

deadlock info

Is there a way to tell which two process' were involved in a deadlck after
it happens?
SQL2K SP3
TIA, ChrisR
ChrisR wrote:
> Is there a way to tell which two process' were involved in a deadlck
> after it happens?
Not after. You can run profiler and trap the deadlock and deadlock chain
events. But you'll need to add the proper SQL event to really see what
was going on. At the very least, you'll need SQL:BatchStarting and
RPC:Starting. better would be to add SQL:StmtStarting for SQL and
SP:StmtStarting for SPs.
David Gugick
Imceda Software
www.imceda.com
|||You can if you're running the output of trace flag 1204 for all connections
to the SQL log.
To do this, issue the following command:
DBCC TRACEON (3605, 1204, -1)
When a deadlock occurs, you'll get a detailed report on the processes, what
objects were locked etc. It's tricky to decipher the output of this trace
flag at first but if you have difficulty post the output back here & I'm
you'll get plenty of help.
Regards,
Greg Linwood
SQL Server MVP
"ChrisR" <bla@.noemail.com> wrote in message
news:OT6gtSozEHA.2568@.TK2MSFTNGP10.phx.gbl...
> Is there a way to tell which two process' were involved in a deadlck after
> it happens?
> --
> SQL2K SP3
> TIA, ChrisR
>

deadlock info

Is there a way to tell which two process' were involved in a deadlck after
it happens?
--
SQL2K SP3
TIA, ChrisRChrisR wrote:
> Is there a way to tell which two process' were involved in a deadlck
> after it happens?
Not after. You can run profiler and trap the deadlock and deadlock chain
events. But you'll need to add the proper SQL event to really see what
was going on. At the very least, you'll need SQL:BatchStarting and
RPC:Starting. better would be to add SQL:StmtStarting for SQL and
SP:StmtStarting for SPs.
--
David Gugick
Imceda Software
www.imceda.com|||You can if you're running the output of trace flag 1204 for all connections
to the SQL log.
To do this, issue the following command:
DBCC TRACEON (3605, 1204, -1)
When a deadlock occurs, you'll get a detailed report on the processes, what
objects were locked etc. It's tricky to decipher the output of this trace
flag at first but if you have difficulty post the output back here & I'm
you'll get plenty of help.
Regards,
Greg Linwood
SQL Server MVP
"ChrisR" <bla@.noemail.com> wrote in message
news:OT6gtSozEHA.2568@.TK2MSFTNGP10.phx.gbl...
> Is there a way to tell which two process' were involved in a deadlck after
> it happens?
> --
> SQL2K SP3
> TIA, ChrisR
>

deadlock info

Is there a way to tell which two process' were involved in a deadlck after
it happens?
SQL2K SP3
TIA, ChrisRChrisR wrote:
> Is there a way to tell which two process' were involved in a deadlck
> after it happens?
Not after. You can run profiler and trap the deadlock and deadlock chain
events. But you'll need to add the proper SQL event to really see what
was going on. At the very least, you'll need SQL:BatchStarting and
RPC:Starting. better would be to add SQL:StmtStarting for SQL and
SP:StmtStarting for SPs.
David Gugick
Imceda Software
www.imceda.com|||You can if you're running the output of trace flag 1204 for all connections
to the SQL log.
To do this, issue the following command:
DBCC TRACEON (3605, 1204, -1)
When a deadlock occurs, you'll get a detailed report on the processes, what
objects were locked etc. It's tricky to decipher the output of this trace
flag at first but if you have difficulty post the output back here & I'm
you'll get plenty of help.
Regards,
Greg Linwood
SQL Server MVP
"ChrisR" <bla@.noemail.com> wrote in message
news:OT6gtSozEHA.2568@.TK2MSFTNGP10.phx.gbl...
> Is there a way to tell which two process' were involved in a deadlck after
> it happens?
> --
> SQL2K SP3
> TIA, ChrisR
>