Consistency Errors

• sh856531

  SSC Veteran

  Points: 269

  More actions

  April 13, 2016 at 5:57 am

  #326432

  Hi all

  Can anyone advise on the best recovery approach for the DBCC output below?

  Customer in question does not have a good backup story and is considering doing an allow data loss repair. I just wanted to persevere and see if there were any alternative options

  Many thanks

  Msg 8966, Level 16, State 2, Line 1

  Unable to read and latch page (1:17812823) with latch type SH. 1(error not found) failed.

  Msg 8966, Level 16, State 2, Line 1

  Unable to read and latch page (1:18309934) with latch type SH. 1(error not found) failed.

  Msg 8966, Level 16, State 2, Line 1

  Unable to read and latch page (1:18449461) with latch type SH. 1(error not found) failed.

  Msg 8966, Level 16, State 2, Line 1

  Unable to read and latch page (1:20123965) with latch type SH. 1(error not found) failed.

  Msg 8966, Level 16, State 2, Line 1

  Unable to read and latch page (1:20123967) with latch type SH. 1(error not found) failed.

  Msg 8966, Level 16, State 2, Line 1

  Unable to read and latch page (1:20134589) with latch type SH. 1(error not found) failed.

  CHECKDB found 0 allocation errors and 6 consistency errors not associated with any single object.

  Msg 8978, Level 16, State 1, Line 1

  Table error: Object ID 1870629707, index ID 1, partition ID 404068565188608, alloc unit ID 404068565188608 (type In-row data). Page (1:15879728) is missing a reference from previous page (1:20123965). Possible chain linkage problem.

  Msg 2533, Level 16, State 1, Line 1

  Table error: page (1:17812823) allocated to object ID 1870629707, index ID 1, partition ID 404068565188608, alloc unit ID 404068565188608 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

  Msg 8976, Level 16, State 1, Line 1

  Table error: Object ID 1870629707, index ID 1, partition ID 404068565188608, alloc unit ID 404068565188608 (type In-row data). Page (1:17812823) was not seen in the scan although its parent (1:19146206) and previous (1:17715204) refer to it. Check any previous errors.

  Msg 8978, Level 16, State 1, Line 1

  Table error: Object ID 1870629707, index ID 1, partition ID 404068565188608, alloc unit ID 404068565188608 (type In-row data). Page (1:17893052) is missing a reference from previous page (1:17812823). Possible chain linkage problem.

  Msg 2533, Level 16, State 1, Line 1

  Table error: page (1:18309934) allocated to object ID 1870629707, index ID 1, partition ID 404068565188608, alloc unit ID 404068565188608 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

  Msg 8976, Level 16, State 1, Line 1

  Table error: Object ID 1870629707, index ID 1, partition ID 404068565188608, alloc unit ID 404068565188608 (type In-row data). Page (1:18309934) was not seen in the scan although its parent (1:16289065) and previous (1:18242352) refer to it. Check any previous errors.

  Msg 8978, Level 16, State 1, Line 1

  Table error: Object ID 1870629707, index ID 1, partition ID 404068565188608, alloc unit ID 404068565188608 (type In-row data). Page (1:18424818) is missing a reference from previous page (1:18309934). Possible chain linkage problem.

  Msg 8978, Level 16, State 1, Line 1

  Table error: Object ID 1870629707, index ID 1, partition ID 404068565188608, alloc unit ID 404068565188608 (type In-row data). Page (1:18840165) is missing a reference from previous page (1:20123967). Possible chain linkage problem.

  Msg 2533, Level 16, State 1, Line 1

  Table error: page (1:20123965) allocated to object ID 1870629707, index ID 1, partition ID 404068565188608, alloc unit ID 404068565188608 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

  Msg 8976, Level 16, State 1, Line 1

  Table error: Object ID 1870629707, index ID 1, partition ID 404068565188608, alloc unit ID 404068565188608 (type In-row data). Page (1:20123965) was not seen in the scan although its parent (1:20151970) and previous (1:20151971) refer to it. Check any previous errors.

  Msg 2533, Level 16, State 1, Line 1

  Table error: page (1:20123967) allocated to object ID 1870629707, index ID 1, partition ID 404068565188608, alloc unit ID 404068565188608 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

  Msg 8976, Level 16, State 1, Line 1

  Table error: Object ID 1870629707, index ID 1, partition ID 404068565188608, alloc unit ID 404068565188608 (type In-row data). Page (1:20123967) was not seen in the scan although its parent (1:18838767) and previous (1:19975745) refer to it. Check any previous errors.

  Msg 8978, Level 16, State 1, Line 1

  Table error: Object ID 1870629707, index ID 1, partition ID 404068565188608, alloc unit ID 404068565188608 (type In-row data). Page (1:20130895) is missing a reference from previous page (1:20134589). Possible chain linkage problem.

  Msg 2533, Level 16, State 1, Line 1

  Table error: page (1:20134589) allocated to object ID 1870629707, index ID 1, partition ID 404068565188608, alloc unit ID 404068565188608 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

  Msg 8976, Level 16, State 1, Line 1

  Table error: Object ID 1870629707, index ID 1, partition ID 404068565188608, alloc unit ID 404068565188608 (type In-row data). Page (1:20134589) was not seen in the scan although its parent (1:14532975) and previous (1:20053803) refer to it. Check any previous errors.

  Msg 8978, Level 16, State 1, Line 1

  Table error: Object ID 1870629707, index ID 3, partition ID 967018518609920, alloc unit ID 967018518609920 (type In-row data). Page (1:17144901) is missing a reference from previous page (1:19842295). Possible chain linkage problem.

  Msg 2533, Level 16, State 1, Line 1

  Table error: page (1:18449461) allocated to object ID 1870629707, index ID 3, partition ID 967018518609920, alloc unit ID 967018518609920 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

  Msg 8976, Level 16, State 1, Line 1

  Table error: Object ID 1870629707, index ID 3, partition ID 967018518609920, alloc unit ID 967018518609920 (type In-row data). Page (1:18449461) was not seen in the scan although its parent (1:15416544) and previous (1:18204837) refer to it. Check any previous errors.

  Msg 8978, Level 16, State 1, Line 1

  Table error: Object ID 1870629707, index ID 3, partition ID 967018518609920, alloc unit ID 967018518609920 (type In-row data). Page (1:18674256) is missing a reference from previous page (1:18449461). Possible chain linkage problem.

  Msg 8928, Level 16, State 1, Line 1

  Object ID 1870629707, index ID 3, partition ID 967018518609920, alloc unit ID 967018518609920 (type In-row data): Page (1:19842295) could not be processed. See other errors for details.

  Msg 8939, Level 16, State 98, Line 1

  Table error: Object ID 1870629707, index ID 3, partition ID 967018518609920, alloc unit ID 967018518609920 (type In-row data), page (1:19842295). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 79824905 and -1.

  Msg 8976, Level 16, State 1, Line 1

  Table error: Object ID 1870629707, index ID 3, partition ID 967018518609920, alloc unit ID 967018518609920 (type In-row data). Page (1:19842295) was not seen in the scan although its parent (1:16339708) and previous (1:19055177) refer to it. Check any previous errors.

  CHECKDB found 0 allocation errors and 22 consistency errors in table 'Table1' (object ID 1870629707).

  CHECKDB found 0 allocation errors and 28 consistency errors in database 'Table2'.

  repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (SmarTrack).