FIX: Stress of Lock Limit Threshold Causes Bufwait Error Message

• Microsoft SQL Server version 6.5

SYMPTOMS

The SQL Server errorlog file may contain one or more of the following errors if there is stress on the SQL Server lock limit threshold:

Error : 1204, Severity: 19, State: 3
SQL Server has run out of LOCKS. Re-run your command when there are
fewer active users, or ask your System Administrator to reconfigure SQL
Server with more LOCKS.

Error : 5904, Severity: 17, State: 0 Background checkpoint process suspended until locks are available.

bufwait: timeout, BUF_IO, bp 0xee55e0, pg 0x26f7, stat 0x1004/0x6, obj 0x8, bpss 0xfa31f0

udread: Operating system error 6(The handle is invalid.) on device 'C:\MSSQL\DATA\devTempdb.DAT' (virtpage 0x020022f7).

EXCEPTION_ACCESS_VIOLATION raised, attempting to create symptom dump

WARNING: Pss found with open sdes; pspid 11, psuid 1, pcurdb 1, system
table entry 0, sdesp 0xf51ba0, objid 1

Error : 826, Severity: 20, State: 1
Attempt made to hold allocation page 11520 that is

Error : 602, Severity: 21, State: 3
Could not find row in Sysindexes for dbid '2', object '16003088',index
'0'. Run DBCC CHECKTABLE on Sysindexes.

Error : 913, Severity: 22, State: 2
Could not find row in Sysdatabases with database id -27352. Run DBCC
CHECKTABLE on Sysdatabases.

WORKAROUND

To work around this problem, use sp_configure to increase the locks value.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.

Keywords : kbusage SSrvGen
Version : 6.5
Platform : WINDOWS
Issue type : kbbug