FIX: Thread Deadlock Causes Checkpoint to Hang in tempdbLast reviewed: December 19, 1997Article ID: Q131662 |
4.21a
WINDOWS
kbprg kbbug4.21a kbfix4.21a.sp3
The information in this article applies to:
BUG# NT: 9992 (4.21a)
SYMPTOMSWhen you execute tempdb-intensive queries involving sorting, under very narrow conditions, a thread deadlock can occur during sort cleanup. This is often difficult to identify because the visible symptoms are ambiguous. However the observed characteristics include a general slowdown, increased blocking, and the checkpoint process hanging in tempdb. It is often possible to login to SQL Server with ISQL.EXE, do SELECTs from user databases, but not possible to run data modification statements in tempdb.
CAUSEWorker threads become deadlocked when deallocating extents during sort cleanup.
WORKAROUNDThe problem is exceedingly narrow in scope and very rare. Because of this and the ambiguous symptoms, this problem should not be suspected until close study has ruled out all other problems. This would include verifying dbcc newalloc and dbcc checkdb are error free on all databases, no errors exist in the SQL errorlog, and any observed blocking or slowdown is not caused by conventional concurrency issues. Slightly changing the application, queries, platform, or SQL configuration may avoid the problem.
STATUSMicrosoft has confirmed this to be a problem in SQL Server version 4.21a. This problem was corrected in the latest U.S. Service Pack for SQL Server version 4.21a. For information on obtaining the Service Pack, please contact your primary support provider.
|
Additional reference words: 4.21a checkpoint
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |