DBCC errors - 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

DBCC errors

Author

Topic

b5white
Starting Member

18 Posts

Posted - 2010-12-15 : 10:23:47

Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -9064597878029942784 (type Unknown), page (2302:-485291838). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29362185 and -14.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -3966433294157807616 (type Unknown), page (9134:-505273598). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29362185 and -10.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -1874682383063121920 (type Unknown), page (65535:-1695563950). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29362185 and -10.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -1866603545382027264 (type Unknown), page (25507:26723200). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29362185 and -1.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:12010680) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (1:12010680) to (1:12018767). 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 0 (type Unknown), page ID (1:12018768) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (1:12018768) to (1:12026855). 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 0 (type Unknown), page ID (1:12026856) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (1:12026856) to (1:12034943). 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 0 (type Unknown), page ID (1:12034944) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (1:12034944) to (1:12043031). 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 0 (type Unknown), page ID (1:12043032) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (1:12043032) to (1:12051119). 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 0 (type Unknown), page ID (1:12051120) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (1:12051120) to (1:12059207). 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 0 (type Unknown), page ID (1:12059208) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (1:12059208) to (1:12067295). 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 0 (type Unknown), page ID (1:12067296) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (1:12067296) to (1:12075383). 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 0 (type Unknown), page ID (1:12075384) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (1:12075384) to (1:12083471). 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 0 (type Unknown), page ID (1:12083472) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (1:12083472) to (1:12091559). 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 0 (type Unknown), page ID (1:12091560) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (1:12091560) to (1:12099647). 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 0 (type Unknown), page ID (1:12099648) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (1:12099648) to (1:12107735). 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 0 (type Unknown), page ID (1:12107736) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (1:12107736) to (1:12115823). 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 0 (type Unknown), page ID (1:12115824) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (1:12115824) to (1:12123911). 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 0 (type Unknown), page ID (1:12123912) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (1:12123912) to (1:12131999). 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 0 (type Unknown), page ID (1:12132000) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (1:12132000) to (1:12140087). 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 0 (type Unknown), page ID (1:12140088) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (1:12140088) to (1:12148175). 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 0 (type Unknown), page ID (1:12148176) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (1:12148176) to (1:12156263). 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 0 (type Unknown), page ID (1:12156264) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (1:12156264) to (1:12164351). 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 501931416485888 (type Unknown), page ID (1:6442291) contains an incorrect page ID in its page header. The PageId in the page header = (5860:1216552020).
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 3346740193673084928 (type Unknown), page (57123:294819651). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29362185 and -10.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 4574811159186571264 (type Unknown), page (17033:-1341480368). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29362185 and -10.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 4727308656092971008 (type Unknown), page ID (1:6442285) contains an incorrect page ID in its page header. The PageId in the page header = (34912:-2120219518).
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 4984331873392066560 (type Unknown), page (14234:1235876111). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29362185 and -1.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 5661348920618319872 (type Unknown), page ID (1:6442286) contains an incorrect page ID in its page header. The PageId in the page header = (41017:1373235655).
CHECKDB found 38 allocation errors and 10 consistency errors not associated with any single object.
Msg 8929, Level 16, State 1, Line 1
Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 11899744092160 (type In-row data): Errors found in off-row data with ID 380558049280 owned by data record identified by RID = (1:6441058:37)
Msg 8929, Level 16, State 1, Line 1
Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 11899744092160 (type In-row data): Errors found in off-row data with ID 380558180352 owned by data record identified by RID = (1:6441058:38)
Msg 8929, Level 16, State 1, Line 1
Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 11899744092160 (type In-row data): Errors found in off-row data with ID 380558311424 owned by data record identified by RID = (1:6441058:39)
Msg 8929, Level 16, State 1, Line 1
Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 11899744092160 (type In-row data): Errors found in off-row data with ID 380558442496 owned by data record identified by RID = (1:6441058:40)
Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data). The off-row data node at page (1:6442266), slot 1, text ID 380558311424 is not referenced.
Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data). The off-row data node at page (1:6442279), slot 0, text ID 380558049280 is not referenced.
Msg 8928, Level 16, State 1, Line 1
Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data): Page (1:6442281) could not be processed. See other errors for details.
Msg 8941, Level 16, State 2, Line 1
Table error: Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data), page (1:6442281). Test (sorted [i].GetOffset () <= m_freeData) failed. Slot 0, offset 0x3c68 is invalid.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data). The off-row data node at page (1:6442281), slot 0, text ID 380558049280 is referenced by page (1:6442279), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data): Page (1:6442282) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data). The off-row data node at page (1:6442282), slot 0, text ID 380558049280 is referenced by page (1:6442279), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data): Page (1:6442283) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data). The off-row data node at page (1:6442283), slot 0, text ID 380558049280 is referenced by page (1:6442279), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data): Page (1:6442284) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data). The off-row data node at page (1:6442284), slot 0, text ID 380558049280 is referenced by page (1:6442279), slot 0, but was not seen in the scan.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data). The off-row data node at page (1:6442284), slot 1, text ID 380558049280 is referenced by page (1:6441058), slot 37, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data): Page (1:6442285) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data). The off-row data node at page (1:6442285), slot 1, text ID 380558114816 is referenced by page (1:6441058), slot 37, but was not seen in the scan.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data). The off-row data node at page (1:6442285), slot 2, text ID 380558180352 is referenced by page (1:6441058), slot 38, but was not seen in the scan.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data). The off-row data node at page (1:6442285), slot 3, text ID 380558245888 is referenced by page (1:6441058), slot 38, but was not seen in the scan.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data). The off-row data node at page (1:6442285), slot 4, text ID 380558311424 is referenced by page (1:6441058), slot 39, but was not seen in the scan.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data). The off-row data node at page (1:6442285), slot 5, text ID 380558376960 is referenced by page (1:6441058), slot 39, but was not seen in the scan.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data). The off-row data node at page (1:6442285), slot 7, text ID 380558442496 is referenced by page (1:6441058), slot 40, but was not seen in the scan.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data). The off-row data node at page (1:6442285), slot 8, text ID 380558508032 is referenced by page (1:6441058), slot 40, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data): Page (1:6442286) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data): Page (1:6442287) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data): Page (1:6442288) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data): Page (1:6442289) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data): Page (1:6442290) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data): Page (1:6442291) could not be processed. See other errors for details.
Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data). The off-row data node at page (1:6442292), slot 0, text ID 380558442496 is not referenced.
Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data). The off-row data node at page (1:6442293), slot 0, text ID 380558442496 is not referenced.
Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 181575685, index ID 0, partition ID 11899744092160, alloc unit ID 71788018805309440 (type LOB data). The off-row data node at page (1:6442294), slot 0, text ID 380558508032 is not referenced.
CHECKDB found 0 allocation errors and 33 consistency errors in table 'Images' (object ID 181575685).
CHECKDB found 38 allocation errors and 43 consistency errors in database 'Checkimaging_back'.

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2010-12-15 : 10:59:03

These errors are not repairable in any way. Restore from a clean backup.

--
Gail Shaw
SQL Server MVP

b5white
Starting Member

18 Posts

Posted - 2010-12-15 : 11:38:10

quote:
Originally posted by GilaMonster

These errors are not repairable in any way. Restore from a clean backup.

OK, I was guessing.
Looks like a perfect storm on the backups.
All 4 backups look like they either failed
or weren't set up correctly.

Just for fun, I'll run RepairWithLoss
and let you know what that says.

Thanks,
Brad.

b5white
Starting Member

18 Posts

Posted - 2010-12-15 : 12:28:58

quote:
Originally posted by b5white

Just for fun, I'll run RepairWithLoss
and let you know what that says.

Most messages are of this level.
Msg 8939, Level 16, State 98, Line 3
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -1866603545382027264 (type Unknown), page (25507:26723200). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 62916617 and -1.
Repairing this error requires other errors to be corrected first.

This appears to be the linchpin that is holding everything up.
Msg 8909, Level 16, State 1, Line 3
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:12010680) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
The system cannot self repair this error.

We'll open a support case.

Thanks,
Brad.

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2010-12-15 : 16:20:31

quote:
Just for fun, I'll run RepairWithLoss

I do kinda know what I'm talking about regarding corruption. There's no minimum error level specified, meaning this is irreparable. Running checkDB with any form of repair is only going to waste your time.

quote:
We'll open a support case.

Don't bother opening a support case. They'll charge you $250 (or more) to tell you exactly what I'm telling you.

This error is not repairable in any way. There's no magic tools to fix this. If you have no backups then you have a hell of a lot of work ahead of you and you will lose a substantial portion of the database.

Script out all objects. Some may fail, but I don't see any indication of damage to the system tables, so you may be lucky.
Export all the data. Some of these will fail. Export what you can, this is the portion that will take loads of work.

Recreate the database and import the data that you got out of the old one. Check your data integrity (you'll likely be missing child or parent records, etc)

--
Gail Shaw
SQL Server MVP

Kristen
Test

22859 Posts

Posted - 2010-12-16 : 10:09:20

Suggest you investigate to see if you can find the cause too - e.g. checking Event Log - most likely caused by hardware fault, which will only reoccur if not repaired.

b5white
Starting Member

18 Posts

Posted - 2011-01-20 : 11:51:03

Just to let you know how this finally turned out.
We recreated the DB and imported all the data.
Amazingly, nearly all the data was recovered.

There were 50,000 dependent child records that
were orphaned, but they appear to be from records
that were purposely deleted. Not sure how that
happened. But we recovered those as well. The client
reviewed and deleted again. Everything else seems
to have come across clean.

Thanks for the help. Brad.

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources