BUG: Concurrent Insert w/ Open Object Reuse May Cause Hang

Last reviewed: December 18, 1997
Article ID: Q178296
The information in this article applies to:
  • Microsoft SQL Server, version 6.5
BUG #: Windows NT: 17420 (6.5)

SYMPTOMS

Concurrent insert activity on a SQL Server with multiple processors when open objects must be reused may cause the server to stop responding. Existing connections will not be able to process commands or receive results. New connections will either stop responding or fail if the server is past the user connection limit.

A primary symptom of this problem is that the following message appears in the SQL Server errorlog:

   spid10   Warning: OPEN OBJECTS parameter may be too low
   spid10   attempt was made to free up descriptors in localdes()
   spid10   Run sp_configure to increase parameter value

WORKAROUND

To work around this problem, increase the 'open objects' configuration value.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

For more information about the 'open objects' configuration option, see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q114843
   TITLE     : INF: Explanation of Open Objects in SQL Server


Additional query words: hang hung lock locked up freeze frozen crashed
crash crashes
Keywords : kbbug6.50 SSrvAdmin
Version : WINNT:6.5
Platform : winnt
Issue type : kbbug
Solution Type : kbworkaround


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: December 18, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.