FIX: Shared Intent Locks Acquired by READTEXT Operation Are Not Released (171867)
The information in this article applies to:
This article was previously published under Q171867
BUG #: 16961 (NT: 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 6.5. This problem has been corrected in Service Pack 5a for Microsoft SQL Server 6.5.For more information, click the following article number to view the article in the Microsoft Knowledge Base: 197177 INF: How to Obtain SQL Server 6.5 Service Pack 5a 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.
| Modification Type: | Major | Last Reviewed: | 3/14/2006 |
|---|
| Keywords: | kbBug kbfix kbusage KB171867 |
|---|
|