BUG: Canceling Striped Table Dump May Cause 1203, dbswritecheck

ID: Q194663

The information in this article applies to:
BUG #: 17654 (SQLBUG_65)

SYMPTOMS

Canceling a striped table dump may cause a series or repeating stream of 1203 errors, or may fail to properly close the dump file, resulting in a dbswritecheck error with an operating system error 32 the next time you attempt to open the dump file.

The SQL Server errorlog will contain the following: 


   dmptable: User attention received
   Error : 1203, Severity: 20, State: 2
   Caller of lock manager is incorrectly trying to unlock an
   unlocked object. spid=42 locktype=2 dbid=8 lockid=761105802.
The locktype will always be 2, and the lockid is the object id of the table being dumped.


WORKAROUND

When doing a DUMP TABLE, specify only a single dump device. The problem does not occur unless you cancel a striped table dump.


STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5.


MORE INFORMATION

After this problem has been encountered, the backup device file must be closed before SQL Server can access it again. To do this, stop and restart SQL Server.

Additional query words: prodsql attention cancel cancelling timeout 


Keywords          : SSrvAdmin SSrvErr_Log SSrvLock SSrvTran_SQL 
Version           : winnt:6.5
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: April 7, 1999