Deadlock LIKE error message in the SQL Server Error log but not Deadlock

Hi, I'm seeing the following entries in the SQL Server error log. Query parallelism is ENABLED in the server. It seems like a Deadlock but it is not I hope.

2010-01-02 01:37:09.36 spid76 DBCC CHECKDB (XPlanner) executed by sa found 0 errors and repaired 0 errors.
2010-01-02 04:51:38.25 spid4 Victim Resource Owner:
2010-01-02 04:51:38.25 spid4 ResType:ExchangeId Stype:'AND' SPID:94 ECID:12 Ec:(0x599CE0C0) Value:0x800ee8a4 Cost:(0/270F)
2010-01-02 04:52:08.25 spid4 Victim Resource Owner:
2010-01-02 04:52:08.25 spid4 ResType:ExchangeId Stype:'AND' SPID:94 ECID:11 Ec:(0xAD11A0C0) Value:0x800eec3c Cost:(0/270F)
2010-01-02 06:00:26.81 spid100 Database SolarWinds: IO is frozen for snapshot

Anyone have any experience with this error message?

Thanks

asked Jan 05 '10 at 03:09 PM in Default

Ken13
31 ● 1 ● 1 ● 1

(comments are locked)

3 answers:

I agree with other post, it is deadlock...

Check the following article... http://support.microsoft.com/kb/832524

Check also Bart Duncan blog... blogs.msdn.com/bartd/archive/2008/09/24/today-s-annoyingly-unwieldy-term-intra-query-parallel-thread-deadlocks.aspx

answered Feb 18 '10 at 09:28 PM

user-1187
21

(comments are locked)

That's a deadlock message. It's showing the victim and the resources that were deadlocked on. You may want to look into that closely because, I think, spid=4 means that it's a system process that was chosen as the deadlock victim.

answered Jan 05 '10 at 03:48 PM

Grant Fritchey ♦♦
64.9k ● 13 ● 20 ● 66

Thans - It looks like deadlock message but I don't see 2 SPIDs involving here(In deadlock sitution genearally we see 2 or more SPIDs in the contention). I almost get this on alternate days.

Jan 05 '10 at 05:57 PM Ken13

(comments are locked)

spid4 is the deadlock monitor, so that's normal. What version of SQL Server are you running? is it 2000? I have a feeling that what you have here may be a parallelism bug, which is why you only see one spid (94) involved

answered Jan 19 '10 at 11:13 PM