Knowledge Base

FIX: An INSERT or UPDATE That Results in a Page Split Might Fail with Error 818

Article ID: 817368

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 #: 364232 (SHILOH_BUGS) - SQL Server 2000 Service Pack 2-based Hotfix
BUG #: 469146 (SHILOH_BUGS) - SQL Server 2000 Service Pack 3-based Hotfix

SYMPTOMS

If a page split occurs on an INSERT or an UPDATE statement, following a DELETE statement that resulted in a page deallocation, an 818 error might be raised back to the client application and written to the SQL Server error log. The client's query will be aborted by this error.

Error: 818, Severity: 19, State: 1
There is no room to hold the buffer resource lock BUF pointer = 0x3357940, page ptr = 0x4bf2e000, pageid = (0x1:0x1de7d), dbid = 2, status = 0xb, file = f:\SQLData\MSSQL\data\tempdb.mdf in SDES SDES pointer = 0x5e4bd00. Contact Technical Support..

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.

There are two versions of this hotfix. One can be applied to SQL Server 2000 Service Pack 2 (SP2), and the other to SQL Server 2000 Service Pack 3 (SP3).

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.

Keywords: kbbug kbfix kbqfe kbsqlserv2000presp4fix kbhotfixserver KB817368

Microsoft KB Archive/817368

Contents