Microsoft KB Archive/929440

From BetaArchive Wiki
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Article ID: 929440

Article Last Modified on 6/19/2007



APPLIES TO

  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 64-bit Edition
  • Microsoft SQL Server 2000 Standard Edition



Bug #: 50000580 (SQL Hotfix)


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
  • Information about whether you must restart the computer after you install the hotfix package
  • Information about whether the hotfix package is replaced by any other hotfix package
  • Information about whether you must make any registry changes
  • The files that are contained in the hotfix package


SYMPTOMS

When you try to update table rows or insert table rows into a table in Microsoft SQL Server 2000, you may receive an error message that resembles one of the following in the SQL Server 2000 Errorlog file:

Error message 1


Error: 644, Severity: 21, State: 5
Could not find the index entry for RID 'Number' in index page (IndexPage), index ID IndexID, database 'TestDB'.

Error message 2


Server: Msg 2511, Level 16, State 1, Line 1
Table error: Object ID Number, Index ID IndexID. Keys out of order on page (IndexPage), slots 184 and 185.

Notes

  • If you update table rows, you may experience this problem because an update operation is a delete operation followed by an insert operation.
  • When this problem occurs, the SQL data in the table rows is not lost. Instead, the table rows are inserted into the table in an incorrect order according to the index key.


CAUSE

This problem occurs if the following conditions are true:

  • When SQL Server inserts the table rows, one of the original pages that contain the table is split into two pages to create sufficient space to insert the table rows.
  • All the table rows are sorted according to an index key.
  • The following behavior occurs:
    • SQL Server tries to insert the table rows in the top half of the original page that will be split.
    • The insert operation causes the table rows in the bottom half of the original page to move to the new page.
    • The index key that is used to sort the table rows causes the new page to have a sort order that comes before the original page.
    Note This behavior is known as a left page split.
  • Before the original page is split into two pages, the original page contains ghost records.
  • The Ghost Record Cleanup thread removes the ghost records from the original page after the original page is split into two pages. However, the thread removes these records before the table rows in the bottom half of the original page are moved to the new page.


RESOLUTION

The installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:

  • The system uses the Advanced Micro Devices (AMD) AMD64 processor architecture or the Intel Extended Memory 64 Technology (EM64T) processor architecture.


Note This issue does not occur on systems that use the Intel Itanium processor architecture.

  • The system is running a 64-bit version of the Microsoft Windows Server operating system.
  • The system is running a 32-bit version of SQL Server 2000.

We have corrected this installation issue in later builds of SQL Server 2000, starting with version 8.00.2244. When a customer who is running SQL Server 2000 on an x64-based system requests this hotfix, we will provide a build that includes this hotfix and that can be installed correctly on an x64-based system. The build that we provide will be version 8.00.2244 or a later version.

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only 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 SQL Server 2000 service pack that contains this hotfix.

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

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.

Prerequisites

You must have Microsoft SQL Server 2000 Service Pack 4 (SP4) installed to apply this hotfix.

For more information about how to obtain SQL Server 2000 Service Pack 4, 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


Restart information

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

Registry information

You do not have to change the registry.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

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 item in Control Panel.

SQL Server 2000 hotfix, 32-bit
File name File version File size Date Time Platform
80sp4-tools.sql Not Applicable 134,628 19-Feb-2006 01:40 Not Applicable
Distmdl.ldf Not Applicable 786,432 06-Dec-2006 01:28 Not Applicable
Distmdl.mdf Not Applicable 2,359,296 06-Dec-2006 01:28 Not Applicable
Dtsui.dll 2000.80.2234.0 1,593,344 06-Dec-2006 01:51 x86
Impprov.dll 2000.80.2234.0 102,400 06-Dec-2006 01:51 x86
Instdist.sql Not Applicable 751,633 29-Nov-2006 15:42 Not Applicable
Msgprox.dll 2000.80.2234.0 94,208 06-Dec-2006 01:51 x86
Msrpjt40.dll 4.10.9424.0 188,473 24-Jan-2006 08:13 x86
Mssdi98.dll 8.11.50523.0 239,104 06-Jun-2005 22:46 x86
Ntwdblib.dll 2000.80.2234.0 290,816 06-Dec-2006 01:51 x86
Odsole70.dll 2000.80.2234.0 69,632 06-Dec-2006 01:51 x86
Osql.exe 2000.80.2234.0 57,344 05-Dec-2006 23:55 x86
Pfclnt80.dll 2000.80.2234.0 430,080 06-Dec-2006 01:51 x86
Procsyst.sql Not Applicable 552,068 17-Jun-2005 00:15 Not Applicable
Qrdrsvc.exe 2000.80.2234.0 192,512 06-Dec-2006 00:00 x86
Replcom.sql Not Applicable 1,216,659 05-Dec-2006 23:44 Not Applicable
Replmerg.exe 2000.80.2234.0 163,840 06-Dec-2006 00:02 x86
Replmerg.sql Not Applicable 1,151,521 05-Dec-2006 23:44 Not Applicable
Replprov.dll 2000.80.2234.0 237,568 06-Dec-2006 01:51 x86
Replrec.dll 2000.80.2234.0 315,392 06-Dec-2006 01:51 x86
Replsub.dll 2000.80.2234.0 270,336 06-Dec-2006 01:51 x86
Replsys.sql Not Applicable 1,096,075 01-Aug-2006 01:21 Not Applicable
Repltran.sql Not Applicable 1,000,691 29-Nov-2006 15:42 Not Applicable
Rinitcom.dll 2000.80.2234.0 278,528 06-Dec-2006 01:51 x86
Semexec.dll 2000.80.2234.0 856,064 06-Dec-2006 01:51 x86
Snapshot.exe 2000.80.2234.0 61,440 06-Dec-2006 00:08 x86
Sp4_serv_qfe.sql Not Applicable 18,810 17-Jun-2005 00:15 Not Applicable
Sqlagent.exe 2000.80.2234.0 323,584 05-Dec-2006 23:46 x86
Sqldiag.exe 2000.80.2234.0 118,784 06-Dec-2006 00:28 x86
Sqldmo.dll 2000.80.2234.0 4,362,240 06-Dec-2006 01:51 x86
Sqldumper.exe Not Applicable 22,528 06-Dec-2006 00:09 x86
Sqlevn70.rll 2000.80.2234.0 45,056 06-Dec-2006 01:51 Not Applicable
Sqlfth75.dll 2000.80.2234.0 102,400 05-Dec-2006 23:54 x86
Sqlservr.exe 2000.80.2234.0 9,175,040 06-Dec-2006 01:49 x86
Sqlsort.dll 2000.80.2234.0 589,824 06-Dec-2006 01:51 x86
Stardds.dll 2000.80.2234.0 176,128 06-Dec-2006 01:51 x86
Svrnetcn.dll 2000.80.2234.0 110,592 06-Dec-2006 01:51 x86
Ums.dll 2000.80.2234.0 35,328 06-Dec-2006 01:51 x86
Xpstar.dll 2000.80.2234.0 311,296 06-Dec-2006 01:51 x86
SQL Server 2000 hotfix, 64-bit
File name File version File size Date Time Platform
80sp4-tools.sql Not Applicable 134,628 19-Feb-2006 01:40 Not Applicable
Distmdl.ldf Not Applicable 786,432 06-Dec-2006 01:28 Not Applicable
Distmdl.mdf Not Applicable 2,359,296 06-Dec-2006 01:28 Not Applicable
Dtsui.dll 2000.80.2234.0 1,593,344 06-Dec-2006 01:51 x86
Impprov.dll 2000.80.2234.0 102,400 06-Dec-2006 01:51 x86
Instdist.sql Not Applicable 751,633 29-Nov-2006 15:42 Not Applicable
Msgprox.dll 2000.80.2234.0 94,208 06-Dec-2006 01:51 x86
Msrpjt40.dll 4.10.9424.0 188,473 24-Jan-2006 08:13 x86
Mssdi98.dll 8.11.50523.0 239,104 06-Jun-2005 22:46 x86
Ntwdblib.dll 2000.80.2234.0 290,816 06-Dec-2006 01:51 x86
Odsole70.dll 2000.80.2234.0 69,632 06-Dec-2006 01:51 x86
Osql.exe 2000.80.2234.0 57,344 05-Dec-2006 23:55 x86
Pfclnt80.dll 2000.80.2234.0 430,080 06-Dec-2006 01:51 x86
Procsyst.sql Not Applicable 552,068 17-Jun-2005 00:15 Not Applicable
Qrdrsvc.exe 2000.80.2234.0 192,512 06-Dec-2006 00:00 x86
Replcom.sql Not Applicable 1,216,659 05-Dec-2006 23:44 Not Applicable
Replmerg.exe 2000.80.2234.0 163,840 06-Dec-2006 00:02 x86
Replmerg.sql Not Applicable 1,151,521 05-Dec-2006 23:44 Not Applicable
Replprov.dll 2000.80.2234.0 237,568 06-Dec-2006 01:51 x86
Replrec.dll 2000.80.2234.0 315,392 06-Dec-2006 01:51 x86
Replsub.dll 2000.80.2234.0 270,336 06-Dec-2006 01:51 x86
Replsys.sql Not Applicable 1,096,075 01-Aug-2006 01:21 Not Applicable
Repltran.sql Not Applicable 1,000,691 29-Nov-2006 15:42 Not Applicable
Rinitcom.dll 2000.80.2234.0 278,528 06-Dec-2006 01:51 x86
Semexec.dll 2000.80.2234.0 856,064 06-Dec-2006 01:51 x86
Snapshot.exe 2000.80.2234.0 61,440 06-Dec-2006 00:08 x86
Sp4_serv_qfe.sql Not Applicable 18,810 17-Jun-2005 00:15 Not Applicable
Sqlagent.exe 2000.80.2234.0 323,584 05-Dec-2006 23:46 x86
Sqldiag.exe 2000.80.2234.0 118,784 06-Dec-2006 00:28 x86
Sqldmo.dll 2000.80.2234.0 4,362,240 06-Dec-2006 01:51 x86
Sqldumper.exe Not Applicable 22,528 06-Dec-2006 00:09 x86
Sqlevn70.rll 2000.80.2234.0 45,056 06-Dec-2006 01:51 Not Applicable
Sqlfth75.dll 2000.80.2234.0 102,400 05-Dec-2006 23:54 x86
Sqlservr.exe 2000.80.2234.0 9,175,040 06-Dec-2006 01:49 x86
Sqlsort.dll 2000.80.2234.0 589,824 06-Dec-2006 01:51 x86
Stardds.dll 2000.80.2234.0 176,128 06-Dec-2006 01:51 x86
Svrnetcn.dll 2000.80.2234.0 110,592 06-Dec-2006 01:51 x86
Ums.dll 2000.80.2234.0 35,328 06-Dec-2006 01:51 x86
Xpstar.dll 2000.80.2234.0 311,296 06-Dec-2006 01:51 x86


STATUS

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

MORE INFORMATION

To confirm that you experience this problem, you must provide the following information to Microsoft Customer Support Services:

  • Determine the page number or page numbers from the error messages that are mentioned in the "Symptoms" section. Page numbers are available in the SQL Server Errorlog files and in the Windows Application event log.
  • Obtain a copy of a transaction log backup file that covers the time during which the page was first used. Typically, this transaction log backup file is the next transaction log backup file that was created after you first receive the error messages that are mentioned in the "Symptoms" section.

For more information, 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


Keywords: kbtshoot kbbug kbfix kbqfe kbpubtypekc kbhotfixserver KB929440