You’re offline. This is a read only version of the page.
275
Hi everyone,
My database got into Recovery Pending and i have got it online by detach and attach the database again but also had to rebuild the log for MyDatabase_model. I have run DBCC CHECKDB and i got some error as below:
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 316659348865024 (type Unknown), page (42754:16777216). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -10.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 21 pages from (1:258816) to (1:266903). See other errors for cause.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 1369938712202313728 (type Unknown), page ID (1:541896) contains an incorrect page ID in its page header. The PageId in the page header = (0:8388608).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 21 pages from (1:541896) to (1:549983). See other errors for cause.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 21 pages from (1:606600) to (1:614687). See other errors for cause.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 31244010184310784 (type Unknown), page ID (1:614688) contains an incorrect page ID in its page header. The PageId in the page header = (110:6357104).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 21 pages from (1:614688) to (1:622775). See other errors for cause.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 2305961757576790016 (type Unknown), page ID (1:792624) contains an incorrect page ID in its page header. The PageId in the page header = (12032:1006660352).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 21 pages from (1:792624) to (1:800711). See other errors for cause.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 281474977431552 (type Unknown), page (1:5). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -14.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 21 pages from (1:897768) to (1:905855). See other errors for cause.
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.
CHECKDB found 11 allocation errors and 0 consistency errors not associated with any single object.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1205579333, index ID 1, partition ID 72057594048020480, alloc unit ID 72057594045333504 (type LOB data), page ID (1:606600) contains an incorrect page ID in its page header. The PageId in the page header = (1:254526).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1205579333, index ID 1, partition ID 72057594048020480, alloc unit ID 72057594045333504 (type LOB data), page ID (1:606600) contains an incorrect page ID in its page header. The PageId in the page header = (1:254526).
CHECKDB found 1 allocation errors and 1 consistency errors in table 'ModelElementData' (object ID 1205579333).
CHECKDB found 12 allocation errors and 1 consistency errors in database 'Mydatabase'.
Is there anyway to fix it? New environment without backup anyway
Regards,
Mark
*This post is locked for comments
I have the same question (0)
You should fix problems highlighted by the integrity check by using backups. From the backup it is possible to restore information on a very granular level down to the exact page with problems.
There are also 2 repair options directly in checkdb without a backup, see if they are helpful:
www.sqlservergeeks.com/repair-the-database-using-dbcc-checkdb
Share
Report
All responses (
Answers (
