Microsoft KB Archive/156662

= BUG: Dynamic Sysprocesses Cursor May Cause Error 616 =

Article ID: 156662

Article Last Modified on 10/16/2003

-

APPLIES TO


 * Microsoft SQL Server 6.5 Standard Edition

-



This article was previously published under Q156662



BUG #: 15943



SYMPTOMS
A dynamic or scrolling cursor created against the sysprocesses, syslocks, or syscurconfigs system tables may cause the following error, if run by more than one client with a symmetric multiprocessor (SMP) computer:

Error : 616, Severity: 20, State: 1

Attempt to hash a previously hashed descriptor for object '-352' in

database 'tempdb'.



WORKAROUND
To work around this problem, change the cursor to INSENSITIVE rather than DYNAMIC.



STATUS
Microsoft has confirmed this to be a problem in Microsoft 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
In addition, this problem may also cause one or more of the following errors:

Error : 605, Severity: 21, State: 1

Attempt to fetch logical page 360 in database 'tempdb' belongs to

object '-384', not to object '-416'.

Error : 16905, Severity: 16, State: 1

The cursor is already open.

Error : 16915, Severity: 16, State: 1

A cursor with the name ' ' already exists.

Getpage: bstat=0x100c/0x1, sstat=0x40, cache

pageno is/should be: objid is/should be:

0x168(360) 0xfffffe80(-384)

0x168(360) 0xfffffe60(-416)

... extent objid 0, mask 0/0, next/prev=0/0

closetable: table already closed for sdes 00abdf58

NOTE: the previous two errors will only occur in the SQL Server errorlog.

Additional query words: getpage closetable

Keywords: kbbug kbother kbusage KB156662

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.