Microsoft KB Archive/828017

= FIX: A SQL Server database may stop responding when you run a transaction that affects many records =

PSS ID Number: 828017

Article Last Modified on 7/30/2004

-

The information in this article applies to:


 * Microsoft SQL Server 2000 (all editions)

-



Bug #: 362926 (SQL Server 8.0)



SYMPTOMS
When you try to run a very large transaction that affects many records at the same time, the Microsoft SQL Server 2000 process that originated the transaction may stop responding. The database may also stop responding until you restart the computer that is running SQL Server.

A call stack that is similar to the following frame fragments is associated with this problem: . . sqlservr!ExecutionContext::WaitForSignal sqlservr!upwait sqlservr!LogMgr::WaitLCFlush sqlservr!LogMgr::InsureLogBlockAvailable sqlservr!LogMgr::RealReserveAndAppend sqlservr!LogMgr::ReserveAndAppend .  . Additionally, a second call stack that is similar to the following frame fragments is associated with this problem: . . sqlservr!LatchBase::Suspend sqlservr!LatchBase::Acquire sqlservr!LogMgr::AllocateLC sqlservr!LogMgr::GetNextLC sqlservr!LogMgr::RealReserveAndAppend . . Other call stacks may also have stacks that are stalled in the LogMgr::RealReserveAndAppend method.

You may also receive the following error messages in the SQL Server error log:

2004-07-19 11:19:37.81 spid57 WARNING: EC 54195558, 0 waited 300 sec. on latch 42d233b0. Not a BUF latch.

2004-07-19 11:19:37.81 spid57 Waiting for type 0x4, current count 0xa, current owning EC 0x42DC1518.

2004-07-19 11:20:56.12 spid54 Time out occurred while waiting for buffer latch type 3,bp 0xd842c0, page 1:1), stat 0xb, object ID 2:99:0, EC 0x453BD4F8 : 0, waittime 300. Continuing to wait.

Note Other problems may also cause the latch time-out errors. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

310834 PRB: Common causes of error message 844 or error message 845 (buffer latch time out errors)



RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft SQL Server 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;%5BLN%5D;CNTACTMS

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this hotfix 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 26-Aug-2003 20:16  2000.80.854.0     528,960  Dtspump.dll 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 04-Aug-2003 18:17                    550,780  Procsyst.sql 22-May-2003 22:57                     19,195  Qfe469571.sql 11-Jul-2003 17:04                  1,084,147  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 13-Aug-2003 16:28                  1,086,797  Replsys.sql 13-Aug-2003 16:28                    986,603  Repltran.sql 29-Jul-2003 20:13  2000.80.819.0     492,096  Semobj.dll 31-May-2003 18:27  2000.80.818.0     172,032  Semobj.rll 05-Aug-2003 21:06                    127,884  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 03-Sep-2003 02:56  2000.80.857.0     188,992  Sqlmmc.dll 02-Sep-2003 23:03  2000.80.857.0     479,232  Sqlmmc.rll 08-Feb-2003 06:40  2000.80.765.0      57,920  Sqlrepss.dll 03-Sep-2003 02:57  2000.80.857.0   7,598,161  Sqlservr.exe 25-Jul-2003 21:44  2000.80.845.0     590,396  Sqlsort.dll 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.

Note: After you apply this fix on your instance of SQL Server 2000, you must also apply the fix that is mentioned in the following article:

831997 FIX: An invalid cursor state occurs after you apply Hotfix 8.00.0859 or later in SQL Server 2000



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
If the problem that is mentioned in the &quot;Symptoms&quot; section of this article occurs, the SQL Server Log Manager for the database stops responding. Therefore, to maintain the safety of the transaction log, the KILL command and the ATTENTION command are not honored in the SQL Server Log Manager. To resolve this problem, restart the computer that is running SQL Server.

Keywords: kbSQLServ2000preSP4fix kbfix kbbug KB828017

Technology: kbAudDeveloper kbSQLServ2000 kbSQLServ2000Search kbSQLServSearch

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© 2004 Microsoft Corporation. All rights reserved.