June 2, 2009 at 5:16 pm
These are all record corruptions in nonclustered index ID 4. My guess is your IO subsystem is causing corruption, which was what corrupted the system table too.
You should be able to offline rebuild the index to fix this, otherwise you're looking at drop/create or repair to rebuild it. If these are the only corruptions, there's no point restoring from your backups the nonclustered index is redundant data anyway.
You also need to find out what's causing these corruptions so you can fix it so they don't happen again to something more critical that can't be repaired.
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
June 2, 2009 at 5:20 pm
Paul, could the previous error have been hiding these, or do you think they're new corruptions?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 2, 2009 at 5:29 pm
If that was the only error in the original CHECKDB output, then no, they weren't masked - as the catalog checks that produce that error are run after the checks that produced the second set of errors.
Holger - was the 8992 error the *only* error in the first set of CHECKDB results? if so, these are new corruptions.
Having it all in German isn't helping things either (no fault of yours Holger!).
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
June 2, 2009 at 10:18 pm
Hi Paul,
yes it was the first and only error.
I will try to use the English MMS console to post English messages (sorry for that)
i will start to rebuild and repair the other errors and then give a feedback.
holger degroot
June 3, 2009 at 12:45 am
Holger Degroot (6/2/2009)
Hi Paul,yes it was the first and only error.
If that's the case, I would suggest two things before you try a fix.
1) Evaluate your IO subsystem - check for errors in event logs or RAID error logs
2) Get that database onto different disks or a different IO system completely.
If you've got new corruptions appearing then there's a serious problem here.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply