BUG: Error 3307 After Canceling Large UPDATE Statement

ID: Q233259

The information in this article applies to:

Microsoft SQL Server version 6.5

BUG #: 18721 (SQLBUG_65)

SYMPTOMS

When canceling a large UPDATE job, you may receive the following error:

Error 3307, Level 21, State 1
Process %d was expected to hold logical lock on page %d.

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

The English version of this fix should have the following file attributes or later:


   Version    File name      Platform
   -----------------------------------------

   6.50.443   Sqlservr.exe   Intel and Alpha

NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:

Q154871 Determining If You Are Eligible for No-Charge Technical Support

WORKAROUND

To work around this problem, try either of the following:

Change the lock escalation thresholds to avoid lock escalation on updates that affect many data pages. For additional information about lock escalation, please see the following article in the Microsoft Knowledge Base:
Q151116 INF: How Tunable Lock Escalation Works
-or-

Request an explicit table lock by using the TABLOCKX optimizer hint in your UPDATE statement.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5.

Additional query words: cancelling canceled cancelled abort aborting aborted terminate terminated terminating


Keywords          : SSrvAdmin kbbug6.50 
Version           : winnt:6.5
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: July 2, 1999