FIX: 1108 Errors with Heavy Tempdb Activity (151988)
The information in this article applies to:
This article was previously published under Q151988 SYMPTOMS
SQL Servers with lots of tempdb activity, sorts, and deadlocks can get 1108
errors in the error log and at the client. The following error message
appears:
Error : 1108, Severity: 21, State: 1
Cannot deallocate extent 944, database 2. Object id 0, index id 0,
status 0 in extent does not match object id -49604, index id 0, status 0
in object being deallocated. Run DBCC CHECKALLOC
CAUSE
You can get 1108 errors in tempdb when there are sorts of small work tables
and some other event occurs such as a deadlock or cancel, causing a
backout. Normally, the client is already backing out for some other reason
so they don't even notice the error, but it does show up in the errorlog.
STATUS
Microsoft has confirmed this to be a problem in Microsoft SQL Server
version 6.5. This problem has been corrected in U.S. Service Pack 1 for
Microsoft SQL Server version 6.5. For more information, contact your
primary support provider.
| Modification Type: | Major | Last Reviewed: | 10/3/2003 |
|---|
| Keywords: | kbBug kbfix kbnetwork KB151988 |
|---|
|