SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 General SQL Server Forums
 Data Corruption Issues
 Page Consistency Errors
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

dataczar
Starting Member

18 Posts

Posted - 01/22/2014 :  10:19:27  Show Profile  Reply with Quote
Can someone let me know if these errors returned from CHECKDB can be repaired.

Msg 8939, Level 16, State 98, Line 2
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page (3:2580902). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -6.
Msg 8909, Level 16, State 1, Line 2
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594169262080 (type Unknown), page ID (3:2580903) contains an incorrect page ID in its page header. The PageId in the page header = (1:3479577).
Msg 8909, Level 16, State 1, Line 2
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594169262080 (type Unknown), page ID (3:2580920) contains an incorrect page ID in its page header. The PageId in the page header = (1:3479594).
Msg 8909, Level 16, State 1, Line 2
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594169262080 (type Unknown), page ID (3:2580921) contains an incorrect page ID in its page header. The PageId in the page header = (1:3479595).
Msg 8909, Level 16, State 1, Line 2
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594169262080 (type Unknown), page ID (3:2580922) contains an incorrect page ID in its page header. The PageId in the page header = (1:3479596).
Msg 8909, Level 16, State 1, Line 2
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594169262080 (type Unknown), page ID (3:2580923) contains an incorrect page ID in its page header. The PageId in the page header = (1:3479597).
Msg 8909, Level 16, State 1, Line 2
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594169262080 (type Unknown), page ID (3:2580924) contains an incorrect page ID in its page header. The PageId in the page header = (1:3479598).
Msg 8909, Level 16, State 1, Line 2
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594169262080 (type Unknown), page ID (3:2580925) contains an incorrect page ID in its page header. The PageId in the page header = (1:3479599).
Msg 8909, Level 16, State 1, Line 2
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594169262080 (type Unknown), page ID (3:2580926) contains an incorrect page ID in its page header. The PageId in the page header = (1:3479600).
Msg 8909, Level 16, State 1, Line 2
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594169262080 (type Unknown), page ID (3:2580927) contains an incorrect page ID in its page header. The PageId in the page header = (1:3479601).
CHECKDB found 0 allocation errors and 10 consistency errors not associated with any single object.
Msg 8928, Level 16, State 1, Line 2
Object ID 288720081, index ID 0, partition ID 72057594092584960, alloc unit ID 72057594099531776 (type In-row data): Page (3:2580902) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 2
Object ID 288720081, index ID 0, partition ID 72057594092584960, alloc unit ID 72057594099531776 (type In-row data): Page (3:2580903) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 2
Object ID 288720081, index ID 0, partition ID 72057594092584960, alloc unit ID 72057594099531776 (type In-row data): Page (3:2580920) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 2
Object ID 288720081, index ID 0, partition ID 72057594092584960, alloc unit ID 72057594099531776 (type In-row data): Page (3:2580921) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 2
Object ID 288720081, index ID 0, partition ID 72057594092584960, alloc unit ID 72057594099531776 (type In-row data): Page (3:2580922) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 2
Object ID 288720081, index ID 0, partition ID 72057594092584960, alloc unit ID 72057594099531776 (type In-row data): Page (3:2580923) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 2
Object ID 288720081, index ID 0, partition ID 72057594092584960, alloc unit ID 72057594099531776 (type In-row data): Page (3:2580924) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 2
Object ID 288720081, index ID 0, partition ID 72057594092584960, alloc unit ID 72057594099531776 (type In-row data): Page (3:2580925) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 2
Object ID 288720081, index ID 0, partition ID 72057594092584960, alloc unit ID 72057594099531776 (type In-row data): Page (3:2580926) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 2
Object ID 288720081, index ID 0, partition ID 72057594092584960, alloc unit ID 72057594099531776 (type In-row data): Page (3:2580927) could not be processed. See other errors for details.
CHECKDB found 0 allocation errors and 10 consistency errors in table 'hsi.transactionxlog' (object ID 288720081).
CHECKDB found 0 allocation errors and 20 consistency errors in database 'OBServer'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (OBServer).

pearlpet26
Starting Member

India
4 Posts

Posted - 01/29/2014 :  04:56:42  Show Profile  Reply with Quote
Yes, using Kernel for SQL Recovery Software your can repair your damaged SQL Server Database instantly. Go to unspammed to know more about SQL repair tool and download the demo application.
Go to Top of Page

elliswhite
Starting Member

36 Posts

Posted - 05/01/2014 :  06:46:14  Show Profile  Reply with Quote
If you have a recent backup then restore it otherwise you can get help from database recovery tool.
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.08 seconds. Powered By: Snitz Forums 2000