January 26, 2012 at 8:26 am
Following error I am getting when I ran DBCC CHECKDB('databasename') WITH NO-INFOMSGS
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 296997425053696 (type Unknown), page (0:-1069739771). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -1.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -10.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -12.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -12.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -14.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -10.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -14.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -10.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -10.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -10.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -10.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -1.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.
CHECKDB found 0 allocation errors and 16 consistency errors not associated with any single object.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:35864) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:35864), slot 0, text ID 94371840 is referenced by page (1:35555), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:35865) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:35865), slot 0, text ID 94371840 is referenced by page (1:35555), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:35866) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:35866), slot 0, text ID 94371840 is referenced by page (1:35555), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:35867) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:35867), slot 0, text ID 94371840 is referenced by page (1:35555), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:35868) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:35868), slot 0, text ID 94371840 is referenced by page (1:35555), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:35869) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:35869), slot 0, text ID 94371840 is referenced by page (1:35555), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:35870) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:35870), slot 0, text ID 94371840 is referenced by page (1:35555), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:35871) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:35871), slot 0, text ID 94371840 is referenced by page (1:35555), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:86184) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:86184), slot 0, text ID 1445199872 is referenced by page (1:85657), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:86185) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:86185), slot 0, text ID 1445199872 is referenced by page (1:85657), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:86186) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:86186), slot 0, text ID 1445199872 is referenced by page (1:85657), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:86187) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:86187), slot 0, text ID 1445199872 is referenced by page (1:85657), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:86188) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:86188), slot 0, text ID 1445199872 is referenced by page (1:85657), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:86189) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:86189), slot 0, text ID 1445199872 is referenced by page (1:85657), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:86190) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:86190), slot 0, text ID 1445199872 is referenced by page (1:85657), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:86191) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:86191), slot 0, text ID 1445199872 is referenced by page (1:85657), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:283812) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data), page (1:283812). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:283812), slot 0, text ID 529661952 is referenced by page (1:283534), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:283813) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:283813), slot 0, text ID 529661952 is referenced by page (1:283534), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:283814) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:283814), slot 0, text ID 529661952 is referenced by page (1:283534), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:283815) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:283815), slot 0, text ID 529661952 is referenced by page (1:283534), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:283816) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:283816), slot 0, text ID 529661952 is referenced by page (1:283534), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:283817) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:283817), slot 0, text ID 529661952 is referenced by page (1:283534), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:283818) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:283818), slot 0, text ID 529661952 is referenced by page (1:283534), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:283819) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:283819), slot 0, text ID 529661952 is referenced by page (1:283534), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:283820) could not be processed. See other errors for details.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:283820), slot 0, text ID 529661952 is referenced by page (1:283534), slot 0, but was not seen in the scan.
Msg 8929, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594087014400 (type In-row data): Errors found in off-row data with ID 94371840 owned by data record identified by RID = (1:11921:2)
Msg 8929, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594087014400 (type In-row data): Errors found in off-row data with ID 1445199872 owned by data record identified by RID = (1:11924:23)
Msg 8929, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594087014400 (type In-row data): Errors found in off-row data with ID 529661952 owned by data record identified by RID = (1:11944:13)
CHECKDB found 0 allocation errors and 54 consistency errors in table 'AllDocStreams' (object ID 373576369).
CHECKDB found 0 allocation errors and 70 consistency errors in database 'WSS_Content_5ce5ed6d-52b4-4eb9-a134-45fb513127fb'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (WSS_Content_5ce5ed6d-52b4-4eb9-a134-45fb513127fb).
Kindly help me to fix this error!
January 26, 2012 at 8:27 am
I strongly recommend you restore from a clean backup since this is a Sharepoint DB. Repair could have very nasty consequences.
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
January 26, 2012 at 8:31 am
The backup also having the same issue, is there any way can I see which page is corrupted?
January 26, 2012 at 8:33 am
May I ask how did you figure out it’s a SharePoint database?
January 26, 2012 at 8:36 am
bashiyam.ganesh (1/26/2012)
The backup also having the same issue, is there any way can I see which page is corrupted?
And earlier backups? Restore is just about the only safe way to handle corruption in a Sharepoint DB.
It's not one page, it's a large number of pages, at least 17.
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
January 26, 2012 at 8:36 am
Dev (1/26/2012)
May I ask how did you figure out it’s a SharePoint database?
CHECKDB found 0 allocation errors and 70 consistency errors in database 'WSS_Content_5ce5ed6d-52b4-4eb9-a134-45fb513127fb'.
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
January 26, 2012 at 8:40 am
I Just joined this organization just couple of days, and I found this error in SQL Sever 2008. Yes this is from Sharepoint DB.
Looks like this problem was there for more than 1 month, during this one month more pages added in sharepoint.
January 26, 2012 at 8:44 am
If you repair this you will lose probably 17 documents from the sharepoint site, no way to tell which ones and no way to fix this without losing that data.
It appears that the damage is limited to the documents table, so that should be the only effects, but it's still a risk considering that sharepoint stores the site's structure in the database.
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
January 26, 2012 at 8:50 am
Yes you are right, this tables stores all types of documents from sharepoint. Also If i ran repair_with_data_loss, I am going to lose only 17 documents or more.
Also, what is the best & safe possible procedure to store sharepoint sites structures in Database.
January 26, 2012 at 9:03 am
Could be more, could be less. There are 17 LOB pages damaged (if I counted correctly), that's about all I can tell you for sure
With sharepoint you have no choice or options regarding how the site structures are stored in the database, that's built into sharepoint's design.
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
January 26, 2012 at 9:29 am
I have test server in place, I am going to restore the data from back and try to run the repair_with_no_data_loss, and see what type of documents I am losing.
This way I can able to see the corrupted ones, what's your suggestion.
Also, can I use FILESTREAM to store these LOB's?
January 26, 2012 at 9:37 am
I have test server in place, so I can restore the data and ran a repair_with_data_loss, this way I can able to find which documents I am losing.
Also, can I use FILESTREAM to store LOB's?
January 26, 2012 at 9:39 am
Sure, that's the best way to see what you're losing. Just bear in mind that if you try and access the damaged documents in the corrupt DB you'll get errors.
As for filestream, I don't know, check with a sharepoint expert.
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
January 26, 2012 at 9:46 am
I have test server in place, so I can store sharepointDB backup to that server and ran repair_with_data_loss, this way I can able to figure-out what type of documents I am losing.
Also, can I use FILESTREAM to store LOB's?
January 26, 2012 at 9:49 am
thanks a lot!
Viewing 15 posts - 1 through 15 (of 17 total)
You must be logged in to reply to this topic. Login to reply