Microsoft KB Archive/195529

= BUG: Cursor with UPDLOCK Hint May Leave Object in Open State =

Article ID: 195529

Article Last Modified on 9/30/2003

-

APPLIES TO


 * Microsoft SQL Server 6.5 Standard Edition

-



This article was previously published under Q195529



BUG #: 17836 (SQLBUG_65)



SYMPTOMS
If a cursor open call encounters a deadlock or the action is canceled, the object that the cursor is based on is left in an open state.

This may eventually lead to open object warnings. Consult the SQL Server error log for open object warning messages.



WORKAROUND
To work around this problem, stop and restart the SQL Server to obtain a clean memory footprint.



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



MORE INFORMATION
Leaving the object in an open state does lead to other improper server behavior. SQL Server may run low on open objects if the error is encountered repeatedly.

Additionally, using queries like sp_who or sp_lock does not show the open object. There are no locks held on the object but the object reference count is artificially inflated.

Additional query words: prodsqlsp sp5errorlog

Keywords: kbbug kbpending KB195529

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.