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
 Consistency errors - how hosed am I?

Author  Topic 

Control Group
Starting Member

1 Post

Posted - 2009-01-28 : 17:56:23
Usual sort of horror story - we've been accumulating 824 errors in this database since 2009-1-9 without knowing it, so we don't have a good backup any more. How we got to this point is a rant for another time.

Right now, I need to identify exactly how far up the creek we are; any assistance in parsing the DBCC CHECKDB results would be much appreciated. Those results, unfortunately, are too massive to post here (hundreds of pages worth), but break down into a few distinct types:

Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -8839967932860596224 (type Unknown), page (25856:1979740672). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12584969 and -1.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -5332261958806667264 (type Unknown), page (0:0). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12584969 and -1.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -5185783918850211840 (type Unknown), page ID (1:2260184) contains an incorrect page ID in its page header. The PageId in the page header = (8192:1912628480).
.
.
.
Msg 8928, Level 16, State 1, Line 1
Object ID 1484565205, index ID 2, partition ID 72057630310465536, alloc unit ID 72057683410812928 (type In-row data): Page (1:2259690) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1484565205, index ID 2, partition ID 72057630310465536, alloc unit ID 72057683410812928 (type In-row data): Page (1:2259691) could not be processed. See other errors for details.
.
.
.
Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 2023919360, index ID 1, partition ID 72057630667309056, alloc unit ID 72057684265861120 (type In-row data). Page (1:2262424) is missing references from parent (unknown) and previous (page (1:2262007)) nodes. Possible bad root entry in system catalog.
Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2023919360, index ID 1, partition ID 72057630667309056, alloc unit ID 72057684265861120 (type In-row data). Parent node for page (1:2262425) was not encountered.

As far as I can see, those errors (8939, 8909, 8928, 8979, 8977) constitute the entirety of the error output. The first batch of errors(all 8939 and 8909) is followed by a block that's more intepretable (and postable):

CHECKDB found 0 allocation errors and 2359 consistency errors not associated with any single object.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 58, index ID 2, partition ID 562949957222400, alloc unit ID 72057594038059008 (type In-row data), page ID (1:2259769) contains an incorrect page ID in its page header. The PageId in the page header = (4978:-2086430897).
CHECKDB found 0 allocation errors and 1 consistency errors in table 'sys.sysbinobjs' (object ID 58).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 69, index ID 2, partition ID 562949957943296, alloc unit ID 72057594039762944 (type In-row data), page ID (1:2259486) contains an incorrect page ID in its page header. The PageId in the page header = (52216:-1).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 69, index ID 2, partition ID 562949957943296, alloc unit ID 72057594039762944 (type In-row data), page ID (1:2259845) contains an incorrect page ID in its page header. The PageId in the page header = (8448:33030147).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 69, index ID 2, partition ID 562949957943296, alloc unit ID 72057594039762944 (type In-row data), page ID (1:2259913) contains an incorrect page ID in its page header. The PageId in the page header = (52216:-1).
CHECKDB found 0 allocation errors and 3 consistency errors in table 'sys.sysrts' (object ID 69).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 74, index ID 1, partition ID 281474981560320, alloc unit ID 281474981560320 (type In-row data), page ID (1:2260131) contains an incorrect page ID in its page header. The PageId in the page header = (11776:905979648).
CHECKDB found 0 allocation errors and 1 consistency errors in table 'sys.syssingleobjrefs' (object ID 74).
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 93, index ID 2, partition ID 562949959516160, alloc unit ID 72057594039173120 (type In-row data), page (44032:20). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12584969 and -1.
CHECKDB found 0 allocation errors and 1 consistency errors in table 'sys.sysxmlplacement' (object ID 93).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 469576711, index ID 2, partition ID 72057594039107584, alloc unit ID 72057594043498496 (type In-row data), page ID (1:2259890) contains an incorrect page ID in its page header. The PageId in the page header = (9984:33030147).
cMsg 8909, Level 16, State 1, Line 1
Table error: Object ID 517576882, index ID 2, partition ID 72057594039304192, alloc unit ID 72057594043695104 (type In-row data), page ID (1:2260040) contains an incorrect page ID in its page header. The PageId in the page header = (9984:33030147).
CHECKDB found 0 allocation errors and 1 consistency errors in table 'DatasetTypeSchemaTypeManagementPackVersion' (object ID 517576882).

There are more blocks of errors, but they're also (like the last several above) easily attributable to user tables. It's really the first batch of 2,359 errors that aren't associated with any single object, as well as the errors tied to the sys.* tables that have me thinking we're completely out of luck.

Notably, the CHECKDB ends with the entirely inauspicious:

...
Msg 8928, Level 16, State 2, Line 1
Object ID 2050106344, index ID 4, partition ID 72057630786912256, alloc unit ID 72057684552712192 (type In-row data): Page (1:2264554) could not be processed. See other errors for details.
CHECKDB found 0 allocation errors and 233 consistency errors in table 'TypedManagedEntity' (object ID 2050106344).
CHECKDB found 0 allocation errors and 6913 consistency errors in database 'OperationsManagerDW'.

Rather than the normal "DBCC execution completed. If DBCC printed error messages, contact your system administrator."

Given our lack of known-good backups, I've already taken a backup of the broken database, and tried running REPAIR_REBUILD (unsurprisingly ineffective) and REBUILD_ALLOW_DATA_LOSS without success. I'm in the process now of trying to extract at least the logical structure of the DB, since reinstalling the software (MSSCOM, in this case) will be a giant PITA. So any input is much appreciated - even if it's just to confirm my "we're SOL" hypothesis, so I don't have to worry I'm missing a good fix.

Thanks!




paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2009-01-28 : 19:08:34
See my answer over on SSC -you're screwed I'm afraid.

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

Suhanti
Starting Member

9 Posts

Posted - 2009-02-23 : 17:33:17

Hello All,

I get this error message everytime I try to run a query, on SHOWCASE SUITE 7.0

IBM (SERIES ACCESS OCBC DRIVER] Communication Link Failure. Comm rc 10054 . CWBCO 1047. The iseries server application disconnected the connection.

I don't know where i should check to work correct this error.
Your assistance is much appreciated!

Thanks
Su
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2009-02-23 : 17:34:58
Suhanti, your error has nothing to do with SQL Server, which is what sqlteam.com is all about. I'd suggest posting your question on a site that deals with the technology you are using, which appears to be IBM iSeries.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

Suhanti
Starting Member

9 Posts

Posted - 2009-02-23 : 17:42:14
hello Tara,
thank you for your advice!

Have a great day
Su
Go to Top of Page

Suhanti
Starting Member

9 Posts

Posted - 2009-02-24 : 01:41:30
hello all,
sorry for bringing this up again, i am now encountering another error message when I attempt to run the query

[IBM] [iSeries Access ODBC] [DB2 UDB]
SQL 0104 - TOKEN, was not valid, Valid tokens: For with Fetch Order Union Except Optimize

What is this? Where can I find the source of error?

Kind regards
Su

Go to Top of Page

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2009-02-24 : 05:11:49
It's not a SQL error. As Tara said, you'll get better responses from a site that deals with IBM iSeries

--
Gail Shaw
SQL Server MVP
Go to Top of Page

eac143
Starting Member

1 Post

Posted - 2009-05-07 : 04:39:34
hello..
is there a solution on this already?

quote:
Originally posted by Suhanti


Hello All,

I get this error message everytime I try to run a query, on SHOWCASE SUITE 7.0

IBM (SERIES ACCESS OCBC DRIVER] Communication Link Failure. Comm rc 10054 . CWBCO 1047. The iseries server application disconnected the connection.

I don't know where i should check to work correct this error.
Your assistance is much appreciated!

Thanks
Su

Go to Top of Page

robvolk
Most Valuable Yak

15732 Posts

Posted - 2009-05-07 : 06:56:47
Locking the thread to prevent further jacking.
Go to Top of Page
   

- Advertisement -