FIX: dbcursorfetchex() Can Cause Blocking in DB-Library

ID: Q151301

The information in this article applies to:

Microsoft SQL Server versions 6.0, 6.5

BUG#: 15039

SYMPTOMS

If a DB-library application calls dbcursorfetch() or dbcursorfetchex() successfully in one thread, subsequent calls to dbcursoropen() or dbclose() from other threads using the same DBPROCESS would be blocked. Sp_who and sp_lock show no blockage on the server side, and the DB-library application would appear to hang.

CAUSES

dbcursorfetch() and dbcursorfetchex() do not release the Semaphore on SUCCEED.

WORKAROUND

Use a separate DBPROCESS for each thread.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. This problem has been corrected in U.S. Service Pack 1 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.


Keywords          : kbprg SSrvProg kbbug6.50 kbbug6.00 kbfix6.50.sp1 
Version           : 6.0 6.5
Platform          : WINDOWS 
Issue type        :

Last Reviewed: March 26, 1999