FIX: Cursor with UPDLOCK Hint May Leave Object in Open State

• Microsoft SQL Server version 6.5

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 version 6.5. This problem has been corrected in U.S. Service Pack 5a for Microsoft SQL Server version 6.5. For information about downloading and installing the latest SQL Server Service Pack, see http://support.microsoft.com/support/sql/.

For more information, contact your primary support provider.

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          : kbbug6.50 kbfix6.50.SP5 
Version           : winnt:6.5
Platform          : winnt 
Issue type        : kbbug 

Last Reviewed: May 4, 1999