Quantcast
Channel: Forum SQL Server Database Engine
Viewing all articles
Browse latest Browse all 15889

SQL consistency based I/O error, help needed

$
0
0

Hello everyone.

I'm new to database errors so I'm not really sure what I should do next. I'm using an accounting program running on SQL Server Express 2005 (9.0 SP3) on a Windows Server 2008R2. While working with a database the SQL Server gave out an error -2147467258, which makes no sense, yes. Associated with this error was a SQL consistency based i/o error. I tried running DBCC CHECKDB and it returned with a lot of errors:

Msg 8967, Level 16, State 216, Line 1
An internal error occurred in DBCC that prevented further processing. Contact Customer Support Services.
DBCC results for 'TK0110'.
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.
Msg 8906, Level 16, State 1, Line 1
Page (1:3588) in database ID 133 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED   0_PCT_FULL'.
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:3588) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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:3588) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8928, Level 16, State 6, Line 1
Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown): Page (1:3588) could not be processed.  See other errors for details.
Msg 8928, Level 16, State 6, Line 1
Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown): Page (1:3589) could not be processed.  See other errors for details.
Msg 8906, Level 16, State 1, Line 1
Page (1:3589) in database ID 133 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED   0_PCT_FULL'.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 128634064356966400 (type Unknown), page (10275:131098). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 130156553 and -1.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 128634064356966400 (type Unknown), page (10275:131098). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 130156553 and -1.
CHECKDB found 6 allocation errors and 2 consistency errors not associated with any single object.
Msg 8906, Level 16, State 1, Line 1
Page (1:3404) in database ID 133 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED   0_PCT_FULL'.
Msg 2575, Level 16, State 1, Line 1
The Index Allocation Map (IAM) page (1:3588) is pointed to by the next pointer of IAM page (0:0) in object ID 846730169, index ID 3, partition ID 72057594098810880, alloc unit ID 72057594102808576 (type In-row data), but it was not detected in the scan.
Msg 7965, Level 16, State 2, Line 1
Table error: Could not check object ID 846730169, index ID 3, partition ID 72057594098810880, alloc unit ID 72057594102808576 (type In-row data) due to invalid allocation (IAM) page(s).
Msg 8906, Level 16, State 1, Line 1
Page (1:3250) in database ID 133 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED   0_PCT_FULL'.
Msg 2575, Level 16, State 1, Line 1
The Index Allocation Map (IAM) page (1:3589) is pointed to by the next pointer of IAM page (0:0) in object ID 846730169, index ID 5, partition ID 72057594098941952, alloc unit ID 72057594102939648 (type In-row data), but it was not detected in the scan.
Msg 7965, Level 16, State 2, Line 1
Table error: Could not check object ID 846730169, index ID 5, partition ID 72057594098941952, alloc unit ID 72057594102939648 (type In-row data) due to invalid allocation (IAM) page(s).
CHECKDB found 4 allocation errors and 2 consistency errors in table 'TAP20111220121130P01' (object ID 846730169).
CHECKDB found 10 allocation errors and 4 consistency errors in database 'TK0110'.

I backed up this data a few days ago, and just made a new backup now to be sure, but as I said, not sure what to do next. Should I try the repair options of DBCC or maybe something else?

I also attached a picture of the error, part of it is in Finnish, but never mind that.. 

-Nexenizer


Viewing all articles
Browse latest Browse all 15889

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>