FIX: Shared Intent Locks Acquired by READTEXT Operation Are Not Released

• Microsoft SQL Server version 6.5

SYMPTOMS

Shared intent locks taken during a READTEXT operation are not released, even after the READTEXT completes. A process that tries to get an exclusive table lock may be blocked by this sh_intent lock.

WORKAROUND

To avoid blocking, minimize requests for exclusive table locks on this table. Testing has shown that any command issued after the READTEXT will cause the sh_intent lock to be released.

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

Trace flag 1200 shows that the sh_intent is acquired but is not being released. Only processes requesting an exclusive table lock will be blocked. This problem occurs only on SQL Server build 6.5.252 and Service Pack 3. In testing, a SELECT @@spid was issued following the READTEXT operation from the same connection. This seemed to clear the sh_intent lock, and was also verified with trace flag 1200.

Additional query words: prodsqlblock sp sp3

Keywords          : kbusage SSrvBCP SSrvGen SSrvLock kbbug6.50.sp3 kbfix6.50.SP5 
Version           : winnt:6.5
Platform          : winnt 
Issue type        : kbbug 

Last Reviewed: June 24, 1999