dbcc checktable error (plss. help)

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

General SQL Server Forums

Data Corruption Issues

dbcc checktable error (plss. help)

Author

Topic

greegy08
Starting Member

19 Posts

Posted - 2009-07-07 : 22:22:26

hi good day!

can someone interpret this error?
i don't want to loss any data in this table. Any idea on how to fix this error without any loss of data? i don't have any clean backup available. Please help!

---------------------------------------------------------------------
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1835869607, index ID 0: Page (1:323460) could not be processed. See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 1835869607, index ID 0, page (1:323460), row 4. Test (ColumnOffsets + (int)sizeof (COLOFF) <= (nextRec - pRec)) failed. Values are 1100 and 1097.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1835869607, index ID 5: Page (1:163241) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1835869607, index ID 5, page (1:163241). Test (m_freeCnt == freeCnt) failed. Values are 496 and 497.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1835869607, index ID 8. Page (1:69784) was not seen in the scan although its parent (1:356875) and previous (1:154698) refer to it. Check any previous errors.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1835869607, index ID 8. Page (1:69785) was not seen in the scan although its parent (1:36595) and previous (1:67849) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1835869607, index ID 8. Page (1:72112) is missing a reference from previous page (1:69785). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1835869607, index ID 8. Page (1:233576) is missing a reference from previous page (1:69784). Possible chain linkage problem.
Server: Msg 2511, Level 16, State 1, Line 1
Table error: Object ID 1835869607, Index ID 10. Keys out of order on page (1:295688), slots 0 and 1.
Server: Msg 8934, Level 16, State 1, Line 1
Table error: Object ID 1835869607, index ID 24. The high key value on page (1:30112) (level 0) is not less than the low key value in the parent (1:397651), slot 53 of the next page (1:30950).
Server: Msg 2511, Level 16, State 1, Line 1
Table error: Object ID 1835869607, Index ID 24. Keys out of order on page (1:397651), slots 52 and 53.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1835869607, index ID 25: Page (1:161170) could not be processed. See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 1835869607, index ID 25, page (1:161170), row 0. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 21 and 16.
DBCC results for 'gbkmut'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1835869607, index ID 34: Page (1:417658) could not be processed. See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 1835869607, index ID 34, page (1:417658), row 60. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 51 and 22.
There are 139153 rows in 21209 pages for object 'gbkmut'.
CHECKTABLE found 0 allocation errors and 15 consistency errors in table 'gbkmut' (object ID 1835869607).
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE (522.dbo.gbkmut ).

---------------------------------------------------------------------
Your reply in this post is highly appreciated.ty

Greegy08
SQl NooB

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2009-07-08 : 02:26:07

Since the minimum repair level is repair_allow_data_loss, and you have no clean backup (why not?), repairing this will result in data loss. No way around that.
Take the DB into single user mode and run DBCC CHECKTABLE (522.dbo.gbkmut, REPAIR_ALLOW_DATA_LOSS)

At a guess, I'd say you'll lose 2 pages of data from this table. You're lucky in that most of the errors appear to be in the nonclustered indexes.

You seem to have a lot of corruption issues with that database. Have you done a root-cause analysis? Checked the IO subsystem?

--
Gail Shaw
SQL Server MVP

greegy08
Starting Member

19 Posts

Posted - 2009-07-08 : 03:06:46

Hi Gail,

I run DBCC CHECKTABLE ('522.dbo.gbkmut', REPAIR_ALLOW_DATA_LOSS)

Results..

Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1835869607, index ID 1. Page (1:323460) was not seen in the scan although its parent (1:328168) and previous (1:323459) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1835869607, index ID 1. Page (1:323461) is missing a reference from previous page (1:323460). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1835869607, index ID 5. Page (1:14572) is missing a reference from previous page (1:163241). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1835869607, index ID 5. Page (1:163241) was not seen in the scan although its parent (1:177401) and previous (1:157776) refer to it. Check any previous errors.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1835869607, index ID 8. Page (1:69784) was not seen in the scan although its parent (1:356875) and previous (1:154698) refer to it. Check any previous errors.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1835869607, index ID 8. Page (1:69785) was not seen in the scan although its parent (1:36595) and previous (1:67849) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1835869607, index ID 8. Page (1:72112) is missing a reference from previous page (1:69785). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1835869607, index ID 8. Page (1:233576) is missing a reference from previous page (1:69784). Possible chain linkage problem.
Server: Msg 2511, Level 16, State 1, Line 1
Table error: Object ID 1835869607, Index ID 10. Keys out of order on page (1:295688), slots 0 and 1.
DBCC results for 'gbkmut'.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
Server: Msg 8934, Level 16, State 2, Line 1
Table error: Object ID 1835869607, index ID 24. The high key value on page (1:30112) (level 0) is not less than the low key value in the parent (1:397651), slot 53 of the next page (1:30950).
Server: Msg 2511, Level 16, State 1, Line 1
Table error: Object ID 1835869607, Index ID 24. Keys out of order on page (1:397651), slots 52 and 53.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1835869607, index ID 25. Page (1:161170) was not seen in the scan although its parent (1:132825) and previous (1:73768) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1835869607, index ID 25. Page (1:235809) is missing a reference from previous page (1:161170). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1835869607, index ID 34. Page (1:25778) is missing a reference from previous page (1:417658). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1835869607, index ID 34. Page (1:417658) was not seen in the scan although its parent (1:237195) and previous (1:411481) refer to it. Check any previous errors.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
Clustered index successfully restored for object 'dbo.gbkmut' in database '522'.
Non-Clustered index successfully restored for object 'dbo.gbkmut, IX_gbkmut_GLCard' in database '522'.
Non-Clustered index successfully restored for object 'dbo.gbkmut, IX_gbkmut_Items' in database '522'.
Non-Clustered index successfully restored for object 'dbo.gbkmut, IX_gbkmut_Resource' in database '522'.
Non-Clustered index successfully restored for object 'dbo.gbkmut, IX_gbkmut_Warehouse' in database '522'.
Non-Clustered index successfully restored for object 'dbo.gbkmut, IX_gbkmut_EntryGuid' in database '522'.
Non-Clustered index successfully restored for object 'dbo.gbkmut, IX_prod_gbkmut' in database '522'.
There are 139153 rows in 21209 pages for object 'gbkmut'.
CHECKTABLE found 0 allocation errors and 15 consistency errors in table 'gbkmut' (object ID 1835869607).
CHECKTABLE fixed 0 allocation errors and 15 consistency errors in table 'gbkmut' (object ID 1835869607).
---------------------------------------------------------------------------------------------------

I think the table is fully fix, but i don't think that i have a data loss in this table.

Greegy08
SQl NooB

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources