April 13, 2007 at 10:03 am
Does anyone know anyhting about this problem and how to fix it.This is in sqls 2005
"All schedulers on Node 0 appear deadlocked due to a large number of worker threads waiting on TRACEWRITE. Process Utilization 0%."
April 13, 2007 at 1:48 pm
I don't even find the message in Sys.Messages. It seems to be a deadlocks problem, you could try to figure it out using SQL Profiler.
April 14, 2007 at 7:39 pm
The means that all threads within SQL process that were running on Node 0 (Thats a New term, inherited due to SQL support for numa architecture) are waiting for resource of TYPE "TRACEWRITE" and are not making any progress.
http://msdn2.microsoft.com/en-us/library/ms179984.aspx
TRACEWRITE:
Occurs when the SQL Trace rowset trace provider waits for either a free buffer or a buffer with events to process.
for information on whats a SOS/scheduler/worker thread refer to SQL Books online or http://blogs.msdn.com/slavao/
so as an action step:
> see if you are getting any memory errors in SQLError Logs.
> Collect DBCC MEMORYSTATUS at the time of issue.
> are you running any server side/client side profiler traces ? if so consider stopping them.
> does this error also produce any MDMP file in SQL Error Log directory? If you, you may want to consider getting in touch with SQL Server support team and take their help.
HTH
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply