FIX: You may receive a 17883 error message when SQL Server 2000 performs a very large hash operation (892205)


The information in this article applies to:

  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Personal Edition
Bug #: 469615 (SQL Server 8.0)
SQL Server 8.0:469615

Article contents

SUMMARY

This article describes the following about this hotfix release:
  • The issues that are fixed by this hotfix package
  • The prerequisites for installing the hotfix package
  • Whether you must restart your computer after you install the hotfix package
  • Whether the hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes
  • The files that are contained in the hotfix package
back to the top

SYMPTOMS

When your computer that is running Microsoft SQL Server 2000 performs a very large hash operation, an error message that is similar to the following may be logged many times to the SQL Server error log:
Date Time server Error: 17883 Severity: 1, State: 0
Date Time server Process 52:0 (94c) UMS Context 0x121A9C98 appears to be non-yielding on Scheduler 3.
For a list of previous hotfixes, see the "Microsoft SQL Server 2000 post-Service Pack 3 or Microsoft SQL Server 2000 post-Service Pack 3a hotfixes" section in the following Microsoft Knowledge Base article:

290211 How to obtain the latest SQL Server 2000 service pack

back to the top

CAUSE

This problem may occur when your computer that is running SQL Server 2000 uses lots of memory during a large hash operation. To reproduce this problem, you will typically require 120 million or more rows of data and hash memory grants of 8 GB or more.

back to the top

RESOLUTION

Hotfix information

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 version of SQL Server 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 telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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.

back to the top

Prerequisites

This hotfix requires Microsoft SQL Server 2000 Service Pack 3 (SP3). For more information about how to obtain SQL Server 2000 Service Pack 3, 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

Additionally, this hotfix requires that you also have SQL Server 2000 hotfix build 2000.80.977 installed. For more information about SQL Server 2000 Post Service Pack 3a hotfix build 2000.80.977, click the following article number to view the article in the Microsoft Knowledge Base:

888007 You receive a "The product does not have a prerequisite update installed" error message when you try to install a SQL Server 2000 post-Service Pack 3 hotfix

back to the top

Restart information

You do not have to restart your computer after you apply this hotfix.

back to the top

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists.

The English version of this hotfix has the file attributes (or later file attributes) 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.

SQL Server 2000, 32-bit versions

   Date         Time   Version         Size       File name
   -----------------------------------------------------------
   14-Jan-2005  19:47  2000.80.1001.0    664,128  Autoplt.dll      
   14-Jan-2005  19:47  2000.80.1001.0     78,400  Console.exe      
   14-Jan-2005  19:47  2000.80.1001.0    332,352  Ctasksui.dll     
   14-Jan-2005  19:47  2000.80.1001.0    315,968  Custtask.dll     
   14-Jan-2005  19:47  2000.80.1001.0     33,340  Dbmslpcn.dll     
   14-Jan-2005  19:47  2000.80.1001.0  1,905,216  Dtspkg.dll       
   14-Jan-2005  19:47  2000.80.1001.0    528,960  Dtspump.dll      
   14-Jan-2005  19:47  2000.80.1001.0     41,536  Dtsrun.exe       
   14-Jan-2005  19:47  2000.80.1001.0  1,557,052  Dtsui.dll        
   14-Jan-2005  19:47  2000.80.1001.0    639,552  Dtswiz.dll       
   14-Jan-2005  19:47  2000.80.1001.0    352,828  Isqlw.exe        
   14-Jan-2005  19:47  2000.80.1001.0     82,492  Itwiz.exe        
   14-Jan-2005  19:47  2000.80.1001.0     90,692  Msgprox.dll      
   31-Dec-2004  19:16  8.11.41022.0      226,304  Mssdi98.dll      
   14-Jan-2005  19:47  2000.80.1001.0     62,024  Odsole70.dll     
   14-Jan-2005  19:48  2000.80.1001.0     25,144  Opends60.dll     
   14-Jan-2005  02:13                     17,576  Opends60.lib
   14-Jan-2005  19:47  2000.80.1001.0     57,904  Osql.exe         
   14-Jan-2005  19:47  2000.80.1001.0    279,104  Pfutil80.dll     
   14-Jan-2005  19:47  2000.80.1001.0    143,940  Qrdrsvc.exe      
   14-Jan-2005  19:47  2000.80.1001.0    221,768  Replprov.dll     
   14-Jan-2005  19:47  2000.80.1001.0    307,784  Replrec.dll      
   14-Jan-2005  19:47  2000.80.1001.0    287,304  Rinitcom.dll     
   14-Jan-2005  19:47  2000.80.1001.0     78,416  Sdiclnt.dll      
   14-Jan-2005  19:47  2000.80.1001.0     66,112  Semmap.dll       
   14-Jan-2005  19:47  2000.80.1001.0     57,916  Semnt.dll        
   14-Jan-2005  19:47  2000.80.1001.0    492,096  Semobj.dll       
   14-Jan-2005  19:47  2000.80.1001.0     53,832  Snapshot.exe     
   14-Jan-2005  19:46  2000.80.1001.0     28,672  Sqlagent.dll     
   14-Jan-2005  19:47  2000.80.1001.0    311,872  Sqlagent.exe     
   14-Jan-2005  19:46  2000.80.1001.0    168,001  Sqlakw32.dll     
   14-Jan-2005  02:23                      4,352  Sqlakw32.lib
   14-Jan-2005  19:47  2000.80.1001.0     33,344  Sqlctr80.dll     
   14-Jan-2005  19:47  2000.80.1001.0    815,676  Sqldata.dll      
   14-Jan-2005  19:47  2000.80.1001.0  4,215,360  Sqldmo.dll       
   14-Jan-2005  19:47                     25,172  Sqldumper.exe    
   14-Jan-2005  19:47  2000.80.1001.0    156,224  Sqlmaint.exe     
   14-Jan-2005  19:47  2000.80.1001.0    180,792  Sqlmap70.dll     
   14-Jan-2005  19:47  2000.80.1001.0    188,992  Sqlmmc.dll       
   14-Jan-2005  19:47  2000.80.1001.0    401,984  Sqlqry.dll       
   14-Jan-2005  19:47  2000.80.1001.0     57,920  Sqlrepss.dll     
   14-Jan-2005  19:48  2000.80.1001.0  7,721,041  Sqlservr.exe     
   14-Jan-2005  19:48  2000.80.1001.0    590,396  Sqlsort.dll      
   14-Jan-2005  19:48  2000.80.1001.0     45,644  Sqlvdi.dll       
   14-Jan-2005  19:48  2000.80.1001.0    106,588  Sqsrvres.dll     
   14-Jan-2005  19:48  2000.80.1001.0     33,340  Ssmsgnet.dll     
   14-Jan-2005  19:48  2000.80.1001.0     33,340  Ssmslpcn.dll     
   14-Jan-2005  19:48  2000.80.1001.0     33,340  Ssmsqlgc.dll     
   14-Jan-2005  19:48  2000.80.1001.0     33,340  Ssmssnet.dll     
   14-Jan-2005  19:48  2000.80.1001.0     82,492  Ssnetlib.dll     
   14-Jan-2005  19:48  2000.80.1001.0     25,148  Ssnmpn70.dll     
   14-Jan-2005  19:48  2000.80.1001.0    123,456  Stardds.dll      
   14-Jan-2005  19:48  2000.80.1001.0    158,240  Svrnetcn.dll     
   14-Jan-2005  19:47  2000.80.1001.0     76,416  Svrnetcn.exe     
   14-Jan-2005  19:48  2000.80.1001.0     49,228  Ums.dll          
   14-Jan-2005  19:48  2000.80.1001.0     74,304  Xplog70.dll      
   14-Jan-2005  19:48  2000.80.1001.0     98,872  Xpweb70.dll      
   31-Dec-2004  19:15  8.0.21213.0       352,256  Msvcr71.dll      
   31-Dec-2004  19:15  2000.80.796.0      57,904  Osql.exe         
   31-Dec-2004  19:15  2000.80.534.0     127,548  Sqdedev.dll      
   31-Dec-2004  19:15  2000.80.194.0     180,290  Sqlunirl.dll     
   14-Jan-2005  02:22  2000.80.1001.0    159,813  Replres.rll
   14-Jan-2005  02:42  2000.80.1001.0    172,032  Semobj.rll
   14-Jan-2005  02:02  2000.80.1001.0     28,672  Sqlevn70.rll
   14-Jan-2005  02:28  2000.80.1001.0    479,232  Sqlmmc.rll

SQL Server 2000 SP3, 64-bit version

   Date         Time   Version         Size        File name      Platform
   -----------------------------------------------------------------------
   15-Jan-2005  02:40  2000.80.1001.0      56,832  Dbmslpcn.dll   IA-64
   15-Jan-2005  02:39  2000.80.1001.0     528,960  Dtspump.dll    x86
   15-Jan-2005  02:40  2000.80.1001.0     185,856  Msgprox.dll    IA-64
   31-Dec-2004  19:10  8.11.41022.0       742,912  Mssdi98.dll    IA-64
   15-Jan-2005  02:40  2000.80.1001.0     151,040  Odsole70.dll   IA-64
   15-Jan-2005  02:41  2000.80.1001.0      27,136  Opends60.dll   IA-64
   14-Jan-2005  19:58                      19,880  Opends60.lib
   15-Jan-2005  02:40  2000.80.1001.0     148,992  Osql.exe       IA-64
   15-Jan-2005  02:40  2000.80.1001.0     353,280  Qrdrsvc.exe    IA-64
   15-Jan-2005  02:40  2000.80.1001.0     534,528  Replprov.dll   IA-64
   15-Jan-2005  02:40  2000.80.1001.0     769,024  Replrec.dll    IA-64
   15-Jan-2005  02:41  2000.80.1001.0     650,240  Rinitcom.dll   IA-64
   15-Jan-2005  02:41  2000.80.1001.0     160,768  Semmap.dll     IA-64
   15-Jan-2005  02:41  2000.80.1001.0     132,608  Semnt.dll      IA-64
   15-Jan-2005  02:40  2000.80.1001.0      88,576  Snapshot.exe   IA-64
   15-Jan-2005  02:39  2000.80.1001.0      10,240  Sqlagent.dll   IA-64
   15-Jan-2005  02:40  2000.80.1001.0   1,055,232  Sqlagent.exe   IA-64
   15-Jan-2005  02:41  2000.80.1001.0      90,112  Sqlboot.dll    IA-64
   15-Jan-2005  02:41  2000.80.1001.0      32,256  Sqlctr80.dll   IA-64
   15-Jan-2005  02:41  2000.80.1001.0     812,032  Sqldata.dll    IA-64
   15-Jan-2005  02:41  2000.80.1001.0  13,845,504  Sqldmo.dll     IA-64
   15-Jan-2005  02:40                      39,936  Sqldumper.exe  IA-64
   15-Jan-2005  02:40  2000.80.1001.0     493,568  Sqlmaint.exe   IA-64
   15-Jan-2005  02:41  2000.80.1001.0      23,040  Sqlmap70.dll   IA-64
   15-Jan-2005  02:41  2000.80.1001.0     152,064  Sqlrepss.dll   IA-64
   15-Jan-2005  02:41  2000.80.1001.0  25,270,272  Sqlservr.exe   IA-64
   15-Jan-2005  02:41  2000.80.1001.0     616,960  Sqlsort.dll    IA-64
   15-Jan-2005  02:41  2000.80.1001.0     120,320  Sqlvdi.dll     IA-64
   15-Jan-2005  02:41  2000.80.1001.0     227,328  Sqsrvres.dll   IA-64
   15-Jan-2005  02:41  2000.80.1001.0      53,760  Ssmslpcn.dll   IA-64
   15-Jan-2005  02:41  2000.80.1001.0      59,904  Ssmsqlgc.dll   IA-64
   15-Jan-2005  02:41  2000.80.1001.0     256,000  Ssnetlib.dll   IA-64
   15-Jan-2005  02:41  2000.80.1001.0      20,992  Ssnmpn70.dll   IA-64
   15-Jan-2005  02:41  2000.80.1001.0     430,080  Svrnetcn.dll   IA-64
   15-Jan-2005  02:40  2000.80.1001.0     185,856  Svrnetcn.exe   IA-64
   15-Jan-2005  02:41  2000.80.1001.0     183,296  Xplog70.dll    IA-64
   15-Jan-2005  02:41  2000.80.1001.0     187,392  Xpweb70.dll    IA-64
   31-Dec-2004  19:10  2000.80.962.0       57,904  Osql.exe       x86
   31-Dec-2004  19:10  2000.80.760.0      269,824  Sqdedev.dll    IA-64
   14-Jan-2005  20:13  2000.80.1001.0     146,432  Replres.rll
   14-Jan-2005  19:58  2000.80.1001.0      19,968  Sqlevn70.rll
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.back to the top

WORKAROUND

To work around this problem, change the join type in the query from a hash join to a merge join.

For more information about hash joins and merge joins, see the "Advanced Query Tuning Concepts" section in the SQL Server Books Online.

back to the top

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

back to the top

MORE INFORMATION

This problem occurs after a period of 60 seconds or more. After this time, the system server process ID (SPID) that performs the hash operation does not yield control of the User Mode Scheduler (UMS). This behavior can cause query delays and timeouts. Also, users cannot log on.

Typically, this problem occurs with SQL Server 2000 when it is on a computer that is running Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems. However, this problem may occur with SQL Server 2000 on a computer that is running the 32-bit versions of Microsoft Windows 2000 or Windows Server 2003 with a smaller number of rows and a smaller number of hash memory grants.

To determine whether you are experiencing this problem, use SQL Profiler. To do this, follow these steps:
  1. Click Start, point to All Programs, point to Microsoft SQL Server, and then click Profiler.
  2. On the File menu, point to New, and then click Trace.
  3. In the Connect to SQL Server dialog box, click the computer that is running SQL Server 2000 that you want in the SQL Server list, choose the authentication option that you want, and then click OK.
  4. On the Events tab, expand Errors and Warnings, click Hash Warning, and then click Add.
  5. On the Data Columns tab, click IntegerData in the Unselected data list, and then click Add.
  6. In theUnselected data list, click EventSubClass, and then click Add.

    Note The IntegerData column will provide the node ID. The EventSubClass column will provide the subevent that may return a hash recursion or a hash bailout.
  7. Click Run to run the trace.

Call stack

The top of the call stack contains information that is similar to the following: 
sqlservr!CHashStrategy::IPartitionFromBucket+0x90
sqlservr!CMatchHashTbl::ComputePrtStats+0x60
sqlservr!CQScanHashMatch::Iterate+0x6d80
sqlservr!CQScanHashMatch::Open+0x220
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packages

For more information about the terminology that Microsoft uses when it corrects software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

back to the top
Modification Type:MinorLast Reviewed:6/1/2006
Keywords:kbbug kbfix kbHotfixServer kbQFE KB892205 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.