Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 DBCC consistency errors

Author  Topic 

imarchenko
Yak Posting Veteran

57 Posts

Posted - 2008-01-11 : 20:29:04
Hello!

I am running SQL Server 2005 (SP2). Recently, DBCC CHECK TABLE reported an error on one of the tables:

...
Table error: Object ID 69575286, index ID 1, partition ID 72057594191216640, alloc unit ID 72057594202161152 (type In-row data). Keys out of order on page (1:261791), slots 8 and 9.
Msg 8986, Level 16, State 1, Line 1
Too many errors found (201) for object ID 69575286. To see all error messages rerun the statement using "WITH ALL_ERRORMSGS".
There are 142506 rows in 6583 pages for object "AllLinks".
CHECKTABLE found 0 allocation errors and 1141 consistency errors in table 'AllLinks' (object ID 69575286).
repair_rebuild is the minimum repair level for the errors found by DBCC CHECKTABLE (STS_Content_TFS.dbo.AllLinks).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

The interesting thing is that I can query entire table without problems. I managed to pull all data into new table and recreate all indexes. My undertanding is that Index ID 1 is a clustered index. It looks to me this error is not very critical although repair_rebuild is advised.

Any thoughts on this matter is greately appreciated.

Igor

eyechart
Master Smack Fu Yak Hacker

3575 Posts

Posted - 2008-01-11 : 21:27:22
chances are you have a hardware problem that caused this corruption.

this is serious btw, so I would open a ticket with microsoft PSS to troubleshoot.



-ec
Go to Top of Page

sqlsquirrel
Starting Member

21 Posts

Posted - 2008-01-14 : 19:22:56
eyechart is correct. To be more thorough run DBCC CHECKDB to make sure other tables are not corrupted. This corruption might be intermittent right now but if in fact it is a hardware issue you will start to see this error appear more and more in your SQL Server error logs. I would start checking the error logs daily for any more reports of this issue.

Brett Davis
Senior SQL Server DBA
For more helpful tips checkout my blog at: http://www.lockergnome.com/sqlsquirrel/
Go to Top of Page
   

- Advertisement -