Article ID: 326999 - View products that this article applies to.
This article was previously published under Q326999
This article has been archived. It is offered "as is" and will no longer be updated.
If lock escalation occurs while an UPDATE query is running that also causes page splits, the server may abort the batch with a 1203 error:
The page number in the error message may differ; however, for this problem it will always be a page (PAG) resource.
Error: 1203, Severity: 20, State: 1 Process ID %d attempting to unlock unowned resource PAG: 7:1:832197.
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:
(https://support.microsoft.com/kb/290211/ )INF: How to Obtain the Latest SQL Server 2000 Service Pack
HotfixThe following hotfix was created before the release of Microsoft SQL Server 2000 Service Pack 3:
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 ------------------------------------------------------------- 18-Jul-2002 20:41 8.00.661 7,467,089 bytes Sqlservr.exe
Because this problem only occurs with lock escalation, eliminating lock escalation during the query can prevent the 1203 error.
For additional information about how to prevent lock escalation, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/323630/ )INF: Resolving Blocking Problems That Are Caused by Lock Escalation in SQL Server
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 SQL Server 2000 Service Pack 3.