Article ID: 821740
Article Last Modified on 11/2/2007
APPLIES TO
- Microsoft SQL Server 2000 Developer Edition
- Microsoft SQL Server 2000 Standard Edition
- Microsoft SQL Server 2000 Enterprise Edition
- Microsoft SQL Server 2000 Personal Edition
- Microsoft SQL Server 2000 Enterprise Edition
- Microsoft SQL Server 2000 Workgroup Edition
- Microsoft SQL Server 2000 Desktop Engine (Windows)
- Microsoft SQL Server 2000 Developer Edition
- Microsoft SQL Server 2000 Enterprise Edition 64-bit
BUG #: 469703 (SHILOH_BUGS)
SYMPTOMS
A Microsoft Distributed Transaction Coordinator (MS DTC) transaction commit operation may cause a blocking scenario on itself. In the SQL Server sysprocesses table output, the SQL Server process ID number (SPID) is less than 50 and shows a self block. For example, the sysprocesses table output may show the following block:
Note MS DTC commit operations always occur on a system task thread.
RESOLUTION
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack
Hotfix information
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name ------------------------------------------------------------------- 31-May-2003 18:45 2000.80.818.0 78,400 Console.exe 25-Jun-2003 01:01 2000.80.818.0 33,340 Dbmslpcn.dll 25-Apr-2003 02:12 786,432 Distmdl.ldf 25-Apr-2003 02:12 2,359,296 Distmdl.mdf 30-Jan-2003 01:55 180 Drop_repl_hotfix.sql 23-Jun-2003 22:40 2000.80.837.0 1,557,052 Dtsui.dll 23-Jun-2003 22:40 2000.80.837.0 639,552 Dtswiz.dll 24-Apr-2003 02:51 747,927 Instdist.sql 03-May-2003 01:56 1,581 Inst_repl_hotfix.sql 08-Feb-2003 06:40 2000.80.765.0 90,692 Msgprox.dll 01-Apr-2003 02:07 1,873 Odsole.sql 05-Apr-2003 01:46 2000.80.800.0 62,024 Odsole70.dll 07-May-2003 20:41 2000.80.819.0 25,144 Opends60.dll 02-Apr-2003 21:48 2000.80.796.0 57,904 Osql.exe 02-Apr-2003 23:15 2000.80.797.0 279,104 Pfutil80.dll 22-May-2003 22:57 19,195 Qfe469571.sql 12-Jun-2003 16:37 1,083,989 Replmerg.sql 04-Apr-2003 21:53 2000.80.798.0 221,768 Replprov.dll 08-Feb-2003 06:40 2000.80.765.0 307,784 Replrec.dll 05-May-2003 00:05 1,085,874 Replsys.sql 01-Jun-2003 01:01 2000.80.818.0 492,096 Semobj.dll 31-May-2003 18:27 2000.80.818.0 172,032 Semobj.rll 29-May-2003 00:29 115,944 Sp3_serv_uni.sql 01-Jun-2003 01:01 2000.80.818.0 4,215,360 Sqldmo.dll 07-Apr-2003 17:44 25,172 Sqldumper.exe 19-Mar-2003 18:20 2000.80.789.0 28,672 Sqlevn70.rll 02-Jul-2003 00:18 2000.80.834.0 180,736 Sqlmap70.dll 08-Feb-2003 06:40 2000.80.765.0 57,920 Sqlrepss.dll 23-Jun-2003 22:40 2000.80.837.0 7,553,105 Sqlservr.exe 08-Feb-2003 06:40 2000.80.765.0 45,644 Sqlvdi.dll 25-Jun-2003 01:01 2000.80.818.0 33,340 Ssmslpcn.dll 01-Jun-2003 01:01 2000.80.818.0 82,492 Ssnetlib.dll 01-Jun-2003 01:01 2000.80.818.0 25,148 Ssnmpn70.dll 01-Jun-2003 01:01 2000.80.818.0 158,240 Svrnetcn.dll 31-May-2003 18:59 2000.80.818.0 76,416 Svrnetcn.exe 30-Apr-2003 23:52 2000.80.816.0 45,132 Ums.dll 02-Jul-2003 00:19 2000.80.834.0 98,816 Xpweb70.dll
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.
MORE INFORMATION
This problem occurs when the MS DTC commit operation tries to update the sysindexes table with appropriate row modifications. If the original transaction activity obtains an exclusive (EX) lock on the sysobjects table or the sysindexes table, the self block may occur at the time of the DTC commit operation. This condition typically occurs when the original transaction activity creates a table or index and also makes additions or subtractions to the table. One of the triggers of the behavior is the open objects option. Carefully review the number of open objects options that the instance of SQL Server 2000 may experience at the time of the problem and the sp_configure setting.
For additional information about this problem and bug #469704, click the following article number to view the article in the Microsoft Knowledge Base:
821740 FIX: Lock Monitor Exception in DeadlockMonitor::ResolveDeadlock
ChildEBP RetAddr Args to Child 09a6f138 77ea9b35 00001324 00000001 00000000 NTDLL!ZwWaitForSingleObject+0xb [i386\usrstubs.asm @ 2004] WARNING: Stack unwind information not available. Following frames may be wrong. 09a6f160 410749ac 00001324 ffffffff 00000001 KERNEL32!WaitForSingleObjectEx+0x71 09a6f17c 41072495 038ba5f0 038c7e00 038ba5f0 ums!UmsThreadScheduler::Switch+0x4c [p:\sql\ums\src\umsthrd.cpp @ 486] 09a6f1a0 410721d6 038ba5f0 4cb24564 09a6f1d8 ums!UmsScheduler::IdleLoop+0x105 [p:\sql\ums\src\umsched.cpp @ 1355] 09a6f1b4 41072d1e ffffffff 00000001 025ad1d8 ums!UmsScheduler::Suspend+0x66 [p:\sql\ums\src\umsched.cpp @ 1181] 09a6f1d8 00401202 ffffffff 00000000 00000000 ums!UmsEvent::Wait+0x8e [p:\sql\ums\src\umsevent.cpp @ 320] 09a6f21c 004378d5 ffffffff 025ad1d8 00000000 sqlservr!ExecutionContext::WaitForSignal+0x1b5 [p:\sql\ntdbms\storeng\dfs\startup\proc.c @ 1058] 09a6f254 00402d66 09a6f2e8 09a6f378 4815b1c0 sqlservr!LockOwner::Sleep+0x13d [p:\sql\ntdbms\storeng\dfs\manager\lckmgr.cpp @ 3273] 09a6f2c8 00404162 09a6f2e8 09a6f378 00000000 sqlservr!lck_lock+0x799 [p:\sql\ntdbms\storeng\dfs\manager\lckmgr.cpp @ 7173] 09a6f310 0040795e 09a6f378 00000003 00000000 sqlservr!SDES::GetLock+0x19d [p:\sql\ntdbms\storeng\dfs\access\access.c @ 870] 09a6f34c 00405c50 00000003 00000001 09a6f378 sqlservr!SDES::AcquireRowLockForScan+0x1e8 [p:\sql\ntdbms\storeng\dfs\access\getnext.c @ 1623] 09a6f3c8 00409a57 00000001 00000000 4815b1c0 sqlservr!SDES::GetBiDi+0x4ae [p:\sql\ntdbms\storeng\dfs\access\getnext.c @ 613] 09a6f41c 00409d0f 00000000 09a6f4bc 09a6f89c sqlservr!CSysScan::FGetNext+0x7f [p:\sql\ntdbms\msql\ddl\sysscan.cpp @ 3544] 09a6f434 0044d245 09a600c4 00000001 00000001 sqlservr!CSysScan::StartScan+0x163 [p:\sql\ntdbms\msql\ddl\sysscan.cpp @ 792] 09a6f49c 004f714a 09a6f89c 5587e178 00000000 sqlservr!CObjectScan::FFindById+0x95 [p:\sql\ntdbms\msql\ddl\sysscan.cpp @ 3711] 09a6f8d0 0080804d 494900c4 055d808b 42b7deb0 sqlservr!createdes+0xbe [p:\sql\ntdbms\storeng\dfs\manager\desmgr.cpp @ 679] 09a6f928 0041719c 42b7db28 494900c4 42b7deb0 sqlservr!chgind_delta+0x78 [p:\sql\ntdbms\storeng\dfs\access\chgsysin.c @ 558] 09a6f95c 0047b973 00000001 42b7db28 3f44b680 sqlservr!XdesRMFull::FlushAllSysIndexCaches+0x88 [p:\sql\ntdbms\storeng\dfs\trans\xdes.cpp @ 6992] 09a6f988 0086896a 3f44a908 00000000 00000000 sqlservr!XdesRMFull::Prepare+0x4f [p:\sql\ntdbms\storeng\dfs\trans\xdes.cpp @ 5813] 09a6f9a4 0086881c 00a1a308 3f44b680 00000000 sqlservr!XactRM::PrepareLocalXact+0x7b [p:\sql\ntdbms\storeng\dfs\trans\xactrm.cpp @ 646] 09a6f9c4 008696ce 77843790 00867868 00000005 sqlservr!XactRM::Commit+0x163 [p:\sql\ntdbms\storeng\dfs\trans\xactrm.cpp @ 472] 09a6f9cc 00867868 00000005 46b0ebc0 00000000 sqlservr!XactRM::CommitDTCXactSinglePhase+0x4b [p:\sql\ntdbms\storeng\dfs\trans\xactrm.cpp @ 1966] 09a6fc14 00864172 00000001 00000335 00a1a3d8 sqlservr!DtcXactRMOnly::PrepareDTCXact+0xc1 [p:\sql\ntdbms\storeng\dfs\trans\xact.cpp @ 3450] 09a6fc6c 004091fe 00bd6780 4cb24098 00000000 sqlservr!ISSResourceAsynch::DoTMWork+0x671 [p:\sql\ntdbms\storeng\dfs\trans\viperrm.cpp @ 2245] 09a6feac 004090d1 09a6fef8 410728a7 760846c8 sqlservr!CWorker::ProcessTskPkt+0xea [p:\sql\ntdbms\storeng\common\ondemand.cpp @ 390] 09a6feb4 410728a7 760846c8 00408cf6 00bd6780 sqlservr!TaskThread+0x14 [p:\sql\ntdbms\storeng\common\ondemand.cpp @ 475] 09a6febc 00408cf6 00bd6780 038ba61c 00000000 ums!UmsSystemUserContext::RunTask+0x7 [p:\sql\ums\src\umsched.cpp @ 1730] 09a6fef8 41075002 038ba5f0 038ba5f0 00000002 sqlservr!SystemTaskEntryPoint+0x98 [p:\sql\ntdbms\storeng\dfs\startup\conn_hdl.c @ 3365] 09a6ff6c 41074698 00bd6788 038bb1a8 09a6ffb4 ums!ProcessWorkRequests+0x272 [p:\sql\ums\src\umsworkq.cpp @ 451] 09a6ff80 7800c9eb 00bd6780 000b32b8 00adb010 ums!ThreadStartRoutine+0x98 [p:\sql\ums\src\umsthrd.cpp @ 263] 09a6ffb4 77e8b2d8 038bb1a8 000b32b8 00adb010 msvcrt!_threadstart+0x57 [thread.c @ 174] 09a6ffec 00000000 7800c994 038bb1a8 00000000 KERNEL32!lstrcmpiW+0xb7
The deadlock monitor detects the problem and tries to resolve it. Because of the nature of commit operation processing, the deadlock monitor cannot resolve the problem, causing bug #469704. The following short stack dump file is logged:
* Short Stack Dump * 00845549 Module(sqlservr+00445549) (DeadlockMonitor::ResolveDeadlock+00000025 Line 583+00000006) * 00845438 Module(sqlservr+00445438) (DeadlockMonitor::SearchAndResolve+00000134 Line 424+00000000) * 004C2D12 Module(sqlservr+000C2D12) (lockMonitor+000002F7 Line 6600+00000000) * 004C2BBC Module(sqlservr+000C2BBC) (lockMonitorThread+000000A4 Line 6414+00000005) * 41072838 Module(UMS+00002838) (ProcessWorkRequests+00000272 Line 451+00000000) * 410725B3 Module(UMS+000025B3) (ThreadStartRoutine+00000098 Line 263+00000007) * 77C37E53 Module(MSVCRT+00027E53) (endthread+000000AA) * 77E7D33B Module(kernel32+0001D33B) (RegisterWaitForInputIdle+00000043)
Keywords: kbbug kbfix kbqfe kbsqlserv2000presp4fix kbhotfixserver KB821740
