BUG: Err 1203 w/ SELECT ORDER BY DESC After an UPDATE in a TranLast reviewed: November 11, 1997Article ID: Q176491 |
The information in this article applies to:
SYMPTOMSIf you run an ORDER BY DESC query after an UPDATE on the same table in a transaction, you may receive the following error message:
Caller of lock manager is incorrectly trying to unlock an unlocked object. spid=%d locktype=%d dbid=%d lockid=%IdThis problem occurs if all of the following conditions are true:
WORKAROUNDTo work around this problem, do any one of the following:
STATUSMicrosoft has confirmed this to be a problem in SQL Server versions 6.5 Service Pack 2 and Service Pack 3. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATION
Steps to Reproduce the ProblemThe following script will demonstrate the problem:
drop table test go create table test (c1 smallint,c2 varchar(200),c3 char(250),c4 int) go /* Create sample data */ declare @wert int select @wert = 1 while @wert < 12 begin insert test values (1,convert(varchar(200),@wert),convert(char(250),@wert),@wert) insert test values (0,convert(varchar(200),@wert+1),convert(char(250),@wert+1),@wert+1) select @wert = @wert + 2 end go create unique clustered index CL_IND ON test (c1, c2) go create nonclustered index NCL_IND on test (c4) go BEGIN TRANSACTION update test set c3 = "X" where c4 = 9 select * from test where c1 = 1 order by c1 DESC COMMIT TRANSACTION |
Additional query words: sp sp2 sp3
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |