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 |
NguyenL71
Posting Yak Master
228 Posts |
Posted - 2008-10-09 : 14:56:39
|
Hi,I am getting the errors below after running DBCC check db. I need to find down what table(s) having problems and probably fix individual table.Does anyone has some suggestions or documents how to fix this. Please don't suggest RESTORE from the latest backup file(s). We already done that and theprevious backup files having the same problems. Any helps would greatly appreciate. SQL 2000.DBCC CHECKDB (ProductionDB) WITH ALL_ERRORMSGSgo-- Need to find down which table(s) having problems.Server: Msg 8909, Level 16, State 1, Line 1Table error: Object ID 0, index ID 0, page ID (7:3154320). The PageId in the page header = (0:0).Server: Msg 8998, Level 16, State 1, Line 1Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify database ID 91 pages from (7:3154320) to (7:3162407). See other errors for cause.Server: Msg 8909, Level 16, State 1, Line 1Table error: Object ID 0, index ID 0, page ID (7:3162408). The PageId in the page header = (0:0).Server: Msg 8998, Level 16, State 1, Line 1Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify database ID 91 pages from (7:3162408) to (7:3170495). See other errors for cause.Server: Msg 8909, Level 16, State 1, Line 1Table error: Object ID 0, index ID 0, page ID (7:3170496). The PageId in the page header = (0:0).Server: Msg 8998, Level 16, State 1, Line 1Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify database ID 91 pages from (7:3170496) to (7:3178583). See other errors for cause.Server: Msg 8909, Level 16, State 1, Line 1Table error: Object ID 0, index ID 0, page ID (7:3178584). The PageId in the page header = (0:0).Server: Msg 8998, Level 16, State 1, Line 1Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify database ID 91 pages from (7:3178584) to (7:3186671). See other errors for cause.Server: Msg 8909, Level 16, State 1, Line 1Table error: Object ID 0, index ID 0, page ID (7:3186672). The PageId in the page header = (0:0).Server: Msg 8998, Level 16, State 1, Line 1Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify database ID 91 pages from (7:3186672) to (7:3194759). See other errors for cause.Server: Msg 8909, Level 16, State 1, Line 1Table error: Object ID 0, index ID 0, page ID (7:3194760). The PageId in the page header = (0:0).Server: Msg 8998, Level 16, State 1, Line 1Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify database ID 91 pages from (7:3194760) to (7:3202847). See other errors for cause.DBCC results for 'ProductionDB'. |
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2008-10-09 : 15:54:22
|
moved to appropriate forum._______________________________________________Causing trouble since 1980Blog: http://weblogs.sqlteam.com/mladenpSpeed up SSMS development: www.ssmstoolspack.com <- version 1.1 out! |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2008-10-09 : 16:39:33
|
The errors are saying that you have corrupt PFS pages (these are allocation bitmaps - see [url]http://www.sqlskills.com/blogs/paul/2008/03/14/InsideTheStorageEngineGAMSGAMPFSAndOtherAllocationMaps.aspx[/url]).These errors cannot be repaired by DBCC CHECKDB, or any other method (documented or undocumented). Trust me on this - I wrote DBCC CHECKDB.The only choice you have, given that your backups are corrupt too, is to extract out as much data as possible into a newly created database. You also need to run diagnostics on your IO subsystem as it seems that's what has caused this corruption (my guess is the PFS pages have been zerod out).ThanksPaul RandalSQL Server MVP, Managing Director, SQLskills.com |
|
|
|
|
|
|
|