Quantcast
Channel: SQLServerCentral » SQL Server 2008 » Data Corruption (SS2K8 / SS2K8 R2) » Latest topics
Viewing all articles
Browse latest Browse all 223

Backup detected error - Checkdb returns errors

$
0
0
Last night's backup failed - message BACKUP detected an error on page (1:1337093).I ran Checkdb and got some errors. First this right at the top:DBCC results for 'NCVLive'.Service Broker Msg 9675, State 1: Message Types analyzed: 14.Service Broker Msg 9676, State 1: Service Contracts analyzed: 6.Service Broker Msg 9667, State 1: Services analyzed: 3.Service Broker Msg 9668, State 1: Service Queues analyzed: 3.Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0.Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0.Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0.Service Broker Msg 9605, State 1: Conversation Priorities analyzed: 0.Msg 8909, Level 16, State 1, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:1337094) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).Msg 8909, Level 16, State 1, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:1337095) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).CHECKDB found 0 allocation errors and 2 consistency errors not associated with any single object.Then these consistency errors on one table:DBCC results for 'ep_careplan'.Msg 8928, Level 16, State 1, Line 1Object ID 122483515, index ID 1, partition ID 72057595327348736, alloc unit ID 72057595334688768 (type In-row data): Page (1:1337093) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 122483515, index ID 1, partition ID 72057595327348736, alloc unit ID 72057595334688768 (type In-row data), page (1:1337093). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 122483515, index ID 1, partition ID 72057595327348736, alloc unit ID 72057595334688768 (type In-row data). Page (1:1337093) was not seen in the scan although its parent (1:775941) and previous (1:1337092) refer to it. Check any previous errors.Msg 8928, Level 16, State 1, Line 1Object ID 122483515, index ID 1, partition ID 72057595327348736, alloc unit ID 72057595334688768 (type In-row data): Page (1:1337094) could not be processed. See other errors for details.Msg 8980, Level 16, State 1, Line 1Table error: Object ID 122483515, index ID 1, partition ID 72057595327348736, alloc unit ID 72057595334688768 (type In-row data). Index node page (1:775941), slot 169 refers to child page (1:1337094) and previous child (1:1337093), but they were not encountered.Msg 8928, Level 16, State 1, Line 1Object ID 122483515, index ID 1, partition ID 72057595327348736, alloc unit ID 72057595334688768 (type In-row data): Page (1:1337095) could not be processed. See other errors for details.Msg 8980, Level 16, State 1, Line 1Table error: Object ID 122483515, index ID 1, partition ID 72057595327348736, alloc unit ID 72057595334688768 (type In-row data). Index node page (1:775941), slot 170 refers to child page (1:1337095) and previous child (1:1337094), but they were not encountered.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 122483515, index ID 1, partition ID 72057595327348736, alloc unit ID 72057595334688768 (type In-row data). Page (1:1337096) is missing a reference from previous page (1:1337095). Possible chain linkage problem.There are 2426647 rows in 38487 pages for object "ep_careplan".CHECKDB found 0 allocation errors and 8 consistency errors in table 'ep_careplan' (object ID 122483515).This: SELECT name FROM sys.indexes WHERE object_id = 122483515 and index_id = 1tells me index id 1 is the Primary Key clustered index.TX log backups are still running without error. My last good full is from two night ago. Last DBCC run clean was 3 days ago. Can this be fixed? Should I restore the last backup and logs elsewhere and bring the table over? Can I even do that? There are Fkeys and a trigger on this table? If necessary, shouldn't I be able to restore the FULL and all the logs up to now and not expect the errors to be present?Should I get the users off this application?Thanks all.

Viewing all articles
Browse latest Browse all 223

Trending Articles