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.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2006-12-04 : 08:15:16
|
| Simon writes "There are error messages in our DBCC CheckDB job. It happens in two of tables. (See below for the sample error messages.)I have found two postings in the forum; but it seems that they are not applicable to my situation:http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=65913http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=55021The errors happen to two of the user tables.So my questions are:1. How to fix these errors?2. Are the records in the DB still good?3. How to prevent this happening again?The database server is running Windows 2000 sp4 and SQL 2000 sp3. It's running on the RAID5 in MS Cluster environment.I really appreciate your assistance. Thank you.The error message samples are:Msg 8974, Sev 16: Text node referenced by more than one node. Object ID 837578022, text, ntext, or image node page (1:130912), slot 27, text ID 25207869603840 is pointed to by page (1:1392667), slot 2 and by page (1:1210230), slot 10. [SQLSTATE 42000]Msg 8961, Sev 16: Table error: Object ID 837578022. The text, ntext, or image node at page (1:130912), slot 30, text ID 25199404974080 does not match its reference from page (1:131226), slot 17. [SQLSTATE 42000]Msg 8974, Sev 16: Text node referenced by more than one node. Object ID 837578022, text, ntext, or image node page (1:130912), slot 30, text ID 25254380437504 is pointed to by page (1:1392667), slot 4 and by page (1:131226), slot 17. [SQLSTATE 42000]Msg 8964, Sev 16: Table error: Object ID 837578022. The text, ntext, or image node at page (1:134162), slot 23, text ID 25204615217152 is not referenced. [SQLSTATE 42000]Msg 8990, Sev 16: CHECKDB found 0 allocation errors and 211 consistency errors in table 'TABLE_ONE' (object ID 837578022). [SQLSTATE 01000]Msg 2536, Sev 16: DBCC results for 'TABLE_TWO'. [SQLSTATE 01000]Msg 8974, Sev 16: Text node referenced by more than one node. Object ID 853578079, text, ntext, or image node page (1:129320), slot 38, text ID 25496001314816 is pointed to by page (1:239021), slot 101 and by page (1:487008), slot 100. [SQLSTATE 42000]Msg 8961, Sev 16: Table error: Object ID 853578079. The text, ntext, or image node at page (1:129320), slot 39, text ID 25199327903744 does not match its reference from page (1:487008), slot 101. [SQLSTATE 42000]Msg 8974, Sev 16: Text node referenced by more than one node. Object ID 853578079, text, ntext, or image node page (1:129320), slot 39, text ID 25496001642496 is pointed to by page (1:239021), slot 102 and by page (1:487008), slot 101. [SQLSTATE 42000]Msg 8964, Sev 16: Table error: Object ID 853578079. The text, ntext, or image node at page (1:136454), slot 1, text ID 25031875559424 is not referenced. [SQLSTATE 42000]Msg 8964, Sev 16: Table error: Object ID 853578079. The text, ntext, or image node at page (1:136454), slot 2, text ID 25031875887104 is not referenced. [SQLSTATE 42000]Msg 8964, Sev 16: Table error: Object ID 853578079. The text, ntext, or image node at page (1:136603), slot 2, text ID 25031875231744 is not referenced. [SQLSTATE 42000]Msg 8928, Sev 16: Object ID 853578079, index ID 255: Page (1:137476) could not be processed. See other errors for details. [SQLSTATE 42000]Msg 8939, Sev 16: Table error: Object ID 853578079, index ID 255, page (1:137476). Test (m_freeCnt == freeCnt) failed. Values are 357 and 525. [SQLSTATE 42000]Msg 2593, Sev 16: There are 1972569 rows in 14051 pages for object 'TABLE_TWO'. [SQLSTATE 01000]Msg 8990, Sev 16: CHECKDB found 0 allocation errors and 166 consistency errors in table 'TABLE_TWO' (object ID 853578079). [SQLSTATE 01000]" |
|
|
Kristen
Test
22859 Posts |
Posted - 2006-12-04 : 08:32:13
|
| These look (to me, but I'm no expert) like pointers to "extended" text records which are corrupted.As such it would seem unlikely to be a hardware fault, more likely perhaps a powercut, incomplete restore etc. (although I would expect SQL Server to "recover" from such scenarios).Might also be a RAID 5 write error - if the Database part wrote all the pages completely, without torn page error, and the Extended TEXT data failed to be written. e.g. to due to a fault on a system with a caching disk controller.Always worth checking EVENT log for any unexpected hardware errors.best way to recover a corrupt database is to restore from backup. I usually find that I can restore the FULL backup and all subsequent TLog backups and get a clean database without losing any data. Assumes that you are using FULL recovery model of course.Certainly first thing to do would be to restore your Backups to a NEW TEMPORARY database, preferably on a different machine, and run a DBCC CHECKDB on the restored database to see if everything is healthy as of the date/time of your backup.Kristen |
 |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2006-12-04 : 22:51:45
|
| This looks like a series of failed writes, where text pointers have moved around between pages but the previous location of the pointers hasn't been updated.Anything in the logs as Kristen suggests?Paul RandalLead Program Manager, Microsoft SQL Server Core Storage Engine (Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.) |
|
|
|
|
|
|
|
|
DBCC CheckDB Error