Article ID: 331885 - View products that this article applies to.
This article was previously published under Q331885
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 362842 (SHILOH_BUGS)
An Update/Delete statement can result in error 1203 during lock escalation. The text for the error message is:
2002-11-07 14:53:06.29 spid52 Error: 1203, Severity: 20, State: 1
2002-11-07 14:53:06.29 spid52 Process ID 52 attempting to unlock unowned resource PAG: 8:1:10842..
Service pack informationTo 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:
(http://support.microsoft.com/kb/290211/ )How to obtain the latest SQL Server 2000 service pack
Hotfix informationNOTE: This fix is intended to be installed on a server that is running SQL Server 2000 Service Pack 2.
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.
NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.
Date Time Version Size File name ------------------------------------------------------------------- 10/24/2002 09:36 AM 8.00.0695 7,293 KB Sqlservr.exe 10/24/2002 09:37 AM 8.00.0695 173 KB Sqlmap70.dll
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.
To support your findings, use SQL Profiler and make sure to capture the SQL:StmtStarting, RPC:Starting, Lock:Escalation, and the ErrorLog events.You will see that the Lock:Escalation event is raised just before the 1203 error is raised. You can use the StartTime data column from SQL Profiler to corelate with the timestamp that is associated with the corresponding 1203 error in the SQL Server error log.
Article ID: 331885 - Last Review: February 27, 2014 - Revision: 10.4