SQL error/dump logs > 80GB - SQL Server Forums

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

SQL error/dump logs > 80GB

Author

Topic

vandora
Starting Member

1 Post

Posted - 2008-11-05 : 23:03:29

When i try to run DBCC CHECKDB, I get

Msg 8921, Level 16, State 1, Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.

Msg 824, Level 24, State 2, Line 1
SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:72483; actual 11:2031068128). It occurred during a read of page (1:72483) in database ID 9 at offset 0x00000023646000 in file 'E:\Database\MYDB.mdf:MSSQL_DBCC9'.

DBCC CHECKTABLE fails for the table MSmerge_genhistory
DBCC results for 'MSmerge_genhistory'.
Msg 8951, Level 16, State 1, Line 13
Table error: table 'MSmerge_genhistory' (ID 2098106515). Data row does not have a matching index row in the index 'unc1MSmerge_genhistory' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 13
Data row (1:20884:1) identified by (generation = 1101300 and UNIQUIFIER = 0) with index values 'guidsrc = 'EA606C1F-EB1C-4D56-A0B1-F3AD7D16737C' and pubid = NULL'.
There are 260084 rows in 7056 pages for object "MSmerge_genhistory".

SimpleSQL
Yak Posting Veteran

85 Posts

Posted - 2008-11-06 : 00:33:58

This indicates corruption in database system tables. Checkdb does make a sanpshot of database, so check if you are runnig out of space in tempdb.
Id you have dumps, you will have to contact MS support for it. But best is to check if you had any HW failures (from system event logs) and go to last known good backup

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2008-11-06 : 01:26:51

The issue here is that CHECKDB read a page from the hidden database snapshot it creates, and the page was corrupt in the snapshot. This should never happen and is a 100% indication that your I/O subsystem is causing problems.

Pages are pushed from the source database into the snapshot as part of the mechanism underlying the consistency checks and the checksum is added to them. The 824 says that the checksum value changed between writing the page to the snapshot and reading it back into DBCC CHECKDB.

You need to run hardware diagnostics, SQLIOsim, and get your databases *off* of that I/O subsystem.

Thanks

Paul S. Randal, SQL Server MVP
Author of SQL 2005 DBCC CHECKDB/repair code
Author & Instructor of Microsoft Certified Master - Database course
Managing Director, SQLskills.com (www.SQLskills.com/blogs/paul)

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources