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
 Consistency error on merge table index

Author  Topic 

readysetstop
Posting Yak Master

123 Posts

Posted - 2007-05-30 : 11:38:37
I'm getting the following error on our merge contents table in one of our DBs:


Msg 8952, Level 16, State 1, Line 1
Table error: Database 'ks241', index 'MSmerge_contents.nc3MSmerge_contents' (ID 1950682047) (index ID 3). Extra or invalid key for the keys:
Msg 8956, Level 16, State 1, Line 1
Index row (1:1893:42) with values (partchangegen = NULL and tablenick = 17665001 and rowguid = AEAE7256-F571-478E-B2B4-D142B47C38C1) points to the data row identified by ().
Msg 8952, Level 16, State 1, Line 1
Table error: Database 'ks241', index 'MSmerge_contents.nc3MSmerge_contents' (ID 1950682047) (index ID 3). Extra or invalid key for the keys:
Msg 8956, Level 16, State 1, Line 1
Index row (1:1893:66) with values (partchangegen = NULL and tablenick = 17665001 and rowguid = B94F1591-33B0-4625-A269-DB9B8B05BCCE) points to the data row identified by ().
CHECKTABLE found 0 allocation errors and 2 consistency errors in table 'MSmerge_contents' (object ID 1950682047).
repair_fast is the minimum repair level for the errors found by DBCC CHECKTABLE (ks241.dbo.MSmerge_contents ).


There are no other corruption issues on the server that I can find. I do not believe there are any current hardware issues, though I am not on site.

What would be the best way to resolve this? Is recreating or defrag/rebuild the index an option, here? Or can I just run a repair on this? Since it's a merge table, I'm a little gun shy, having limited experience with replication.

Thanks.

____________________________________________________________________________________
"Believe in those who are seeking the truth. Doubt those who say they have found it." -Andre Gide

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2007-05-30 : 12:48:40
Well, it's just a non-clustered index with a couple of extra rows so you can just rebuild it and that should fix it. I'm concerned why it happened though. Has it happened before? Any unusual events on the server?

What version and SP level are you on?

Paul Randal
Principal Lead Program Manager, Microsoft SQL Server Core Storage Engine
(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)
http://blogs.msdn.com/sqlserverstorageengine/default.aspx
Go to Top of Page

readysetstop
Posting Yak Master

123 Posts

Posted - 2007-05-30 : 13:00:38
SQL is version 8.0.2039. I don't see any other unusual events on there. (This is, though, the first time I'm looking at this box. First day in the new job...)

I'll go ahead, backup, and rebuild. Thanks again for the input.

____________________________________________________________________________________
"Believe in those who are seeking the truth. Doubt those who say they have found it." -Andre Gide
Go to Top of Page

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2007-05-30 : 13:06:12
Ah - in that case, can you get hold of any previous output from CHECKDB? And I'm curious why they're only running CHECKTABLE instead of CHECKDB?

Paul Randal
Principal Lead Program Manager, Microsoft SQL Server Core Storage Engine
(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)
http://blogs.msdn.com/sqlserverstorageengine/default.aspx
Go to Top of Page

readysetstop
Posting Yak Master

123 Posts

Posted - 2007-05-30 : 13:19:47
They are running CHECKDB, I believe. Hard to tell since everything's in maintenance plans and I haven't got it all pinned down yet. (I can't even access the text logs yet...) I ran CHECKTABLE based on the output I got from the error in the replication monitor. Sorry, but I don't have any previous CHECKDB results to show you. I'll post it all next time I run into the issue.

p.s., Rebuild worked like a charm, and replication is running again. Thanks for the help.

____________________________________________________________________________________
"Believe in those who are seeking the truth. Doubt those who say they have found it." -Andre Gide
Go to Top of Page
   

- Advertisement -