December 2, 2008 at 6:02 pm
Do not have a good backup of the DB and it appears the inconsistency began around 11/12 during a LUN move of the SAN housing the DB.
DBCC with no data loss outputs the following (successes omitted for easier reading) - it ultimately suggests to run the DBCC again with data loss enabled:
----
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -578979977, index ID 56797, page ID (7:249900). The PageId in the page header = (56797:-578979977).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -7997301, index ID 65280, page ID (7:251980). The PageId in the page header = (59396:1996443888).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -2923716, index ID 58950, page ID (7:231052). The PageId in the page header = (16874:-1019017460).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -578979977)' (object ID -578979977).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -7997301)' (object ID -7997301).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -2923716)' (object ID -2923716).
DBCC results for 'tkcsdb'.
DBCC results for 'sysproperties'.
There are 0 rows in 0 pages for object 'sysproperties'.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 350, index ID 45963, page ID (7:106204). The PageId in the page header = (10366:728116350).
DBCC results for 'sysfilegroups'.
There are 10 rows in 1 pages for object 'sysfilegroups'.
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 350)' (object ID 350).
DBCC results for 'ERPARAMVALTYPE'.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 812017200, index ID 12390, page ID (7:265116). The PageId in the page header = (26160:808464486).
There are 8 rows in 1 pages for object 'ERPARAMVALTYPE'.
DBCC results for 'PROBATIONQUALIFIER'.
There are 0 rows in 0 pages for object 'PROBATIONQUALIFIER'.
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 812017200)' (object ID 812017200).
DBCC results for 'RPTSTAFFEFFCNCY'.
There are 0 rows in 0 pages for object 'RPTSTAFFEFFCNCY'.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1311592983, index ID 35201, page ID (3:303595). The PageId in the page header = (22519:1462266723).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1313431364, index ID 2573, page ID (7:193660). The PageId in the page header = (20304:1230982477).
DBCC results for 'HFCNSTRTYPE'.
There are 188 rows in 3 pages for object 'HFCNSTRTYPE'.
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 1311592983)' (object ID 1311592983).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 1313431364)' (object ID 1313431364).
DBCC results for 'UICOMPONENT'.
There are 9 rows in 1 pages for object 'UICOMPONENT'.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1342204416, index ID 17803, page ID (3:346059). The PageId in the page header = (65504:-216209354).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 1342204416)' (object ID 1342204416).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1509966336, index ID 0, page ID (5:786153). The PageId in the page header = (0:822097152).
DBCC results for 'PAYCODE'.
There are 368 rows in 8 pages for object 'PAYCODE'.
The repair level on the DBCC statement caused this repair to be bypassed.
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 1509966336)' (object ID 1509966336).
DBCC results for 'PAYRULEHOLIDAYMM'.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1634623853, index ID 24950, page ID (7:276252). The PageId in the page header = (11875:1714320237).
There are 12226 rows in 43 pages for object 'PAYRULEHOLIDAYMM'.
The repair level on the DBCC statement caused this repair to be bypassed.
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 1634623853)' (object ID 1634623853).
DBCC results for 'ORGIDS'.
There are 2 rows in 1 pages for object 'ORGIDS'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 0: Page (7:143180) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 0, page (7:143180). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 0: Page (7:160636) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 0, page (7:160636). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
DBCC results for 'WFCTOTAL'.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 0: Page (7:193659) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 0, page (7:193659). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 0: Page (7:193660) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 0: Page (7:221436) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 0, page (7:221436). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 0: Page (7:231051) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 0, page (7:231051). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 0: Page (7:231052) could not be processed. See other errors for details.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 0: Page (7:234876) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 0, page (7:234876). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 0: Page (7:249899) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 0, page (7:249899). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 0: Page (7:249900) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 0: Page (7:251979) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 0, page (7:251979). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 0: Page (7:251980) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 0: Page (7:265115) could not be processed. See other errors for details.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
Server: Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1794105432, index ID 0, page (7:265115). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 0: Page (7:265116) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 0: Page (7:269804) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 0, page (7:269804). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 0: Page (7:276251) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 0, page (7:276251). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 0: Page (7:276252) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 0: Page (7:682847) could not be processed. See other errors for details.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
Server: Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1794105432, index ID 0, page (7:682847). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:143180) was not seen in the scan although its parent (7:501091) and previous (7:143179) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:143181) is missing a reference from previous page (7:143180). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:160636) was not seen in the scan although its parent (7:297117) and previous (7:160635) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:160637) is missing a reference from previous page (7:160636). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:193659) was not seen in the scan although its parent (7:499292) and previous (7:193658) refer to it. Check any previous errors.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Index node page (7:499292), slot 40 refers to child page (7:193660) and previous child (7:193659), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:193661) is missing a reference from previous page (7:193660). Possible chain linkage problem.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:221436) was not seen in the scan although its parent (7:687252) and previous (7:221435) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:221437) is missing a reference from previous page (7:221436). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:231051) was not seen in the scan although its parent (7:720671) and previous (7:231050) refer to it. Check any previous errors.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Index node page (7:720671), slot 33 refers to child page (7:231052) and previous child (7:231051), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:231053) is missing a reference from previous page (7:231052). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:234876) was not seen in the scan although its parent (7:978158) and previous (7:564879) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:234877) is missing a reference from previous page (7:234876). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:249899) was not seen in the scan although its parent (7:493456) and previous (7:249898) refer to it. Check any previous errors.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Index node page (7:493456), slot 69 refers to child page (7:249900) and previous child (7:249899), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:249901) is missing a reference from previous page (7:249900). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:251979) was not seen in the scan although its parent (7:994813) and previous (7:251978) refer to it. Check any previous errors.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Index node page (7:994813), slot 70 refers to child page (7:251980) and previous child (7:251979), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:251981) is missing a reference from previous page (7:251980). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:265115) was not seen in the scan although its parent (7:501051) and previous (7:265114) refer to it. Check any previous errors.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Index node page (7:501051), slot 11 refers to child page (7:265116) and previous child (7:265115), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:265117) is missing a reference from previous page (7:265116). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:269804) was not seen in the scan although its parent (7:497678) and previous (7:269803) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:269805) is missing a reference from previous page (7:269804). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:276251) was not seen in the scan although its parent (7:1018474) and previous (7:276250) refer to it. Check any previous errors.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Index node page (7:1018474), slot 7 refers to child page (7:276252) and previous child (7:276251), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:276253) is missing a reference from previous page (7:276252). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:682847) was not seen in the scan although its parent (7:177479) and previous (7:682846) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 1. Page (7:682872) is missing a reference from previous page (7:682847). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 3: Page (3:346058) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 3, page (3:346058). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 3. Page (3:346058) was not seen in the scan although its parent (3:417800) and previous (3:346057) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 3: Page (3:346059) could not be processed. See other errors for details.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 3. Index node page (3:417800), slot 151 refers to child page (3:346059) and previous child (3:346058), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 3. Page (3:346060) is missing a reference from previous page (3:346059). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 4: Page (5:786152) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 4, page (5:786152). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 4. Page (5:786152) was not seen in the scan although its parent (5:684447) and previous (5:786151) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 4: Page (5:786153) could not be processed. See other errors for details.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 4. Index node page (5:684447), slot 101 refers to child page (5:786153) and previous child (5:786152), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 4. Page (5:786154) is missing a reference from previous page (5:786153). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 5: Page (7:106203) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 5, page (7:106203). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 5. Page (7:106203) was not seen in the scan although its parent (7:774687) and previous (7:106202) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1794105432, index ID 5: Page (7:106204) could not be processed. See other errors for details.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 5. Index node page (7:774687), slot 1 refers to child page (7:106204) and previous child (7:106203), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1794105432, index ID 5. Page (7:106205) is missing a reference from previous page (7:106204). Possible chain linkage problem.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
There are 28920345 rows in 571008 pages for object 'WFCTOTAL'.
CHECKDB found 0 allocation errors and 78 consistency errors in table 'WFCTOTAL' (object ID 1794105432).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1842105603, index ID 4: Page (3:303594) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1842105603, index ID 4, page (3:303594). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1842105603, index ID 4. Page (3:303594) was not seen in the scan although its parent (3:305047) and previous (3:303593) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1842105603, index ID 4: Page (3:303595) could not be processed. See other errors for details.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1842105603, index ID 4. Index node page (3:305047), slot 198 refers to child page (3:303595) and previous child (3:303594), but they were not encountered.
DBCC results for 'TIMESHEETITEM'.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1842105603, index ID 4. Page (3:303596) is missing a reference from previous page (3:303595). Possible chain linkage problem.
The repair level on the DBCC statement caused this repair to be bypassed.
There are 8625115 rows in 290940 pages for object 'TIMESHEETITEM'.
CHECKDB found 0 allocation errors and 6 consistency errors in table 'TIMESHEETITEM' (object ID 1842105603).
DBCC results for 'MYWTKEMPLOYEE'.
There are 64530 rows in 311 pages for object 'MYWTKEMPLOYEE'.
CHECKDB found 0 allocation errors and 94 consistency errors in database 'tkcsdb'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (tkcsdb repair_rebuild).
DBCC execution completed. If DBCC printed error messages, contact your system administrator
------------
When we run the DBCC without indexes, we get fewer errors (34). I have a few questions before proceeding:
Will the log results of the fix with data loss give us a hint as to the specific data lost?
Is there any way to gauge how much data we may lose based on the erros above?
Yes, we need a DBA. Thanks in advance.
December 2, 2008 at 6:53 pm
Note that this is a 2005 specific forum - there is a 7.0+2000 forum (and you're running SQL 2000 - from the DBCC output) - not a big deal but posting in the right forum helps us figure out what advice to give.
There's no easy way to tell what data will be lost and it isn't logged anywhere - apart from the fact that it will tell you which pages it deletes. I thought about adding a lost+found equivalent for 2005 but it didn't make it. For 2000, definitely not.
You're going to lose (in fact you've already lost - because those pages are unreadable) a bunch of pages in clustered index leaf-levels (i.e. table data). You can do a couple of things to try to figure out what gets deleted:
1) backup the corrupt database, restore it with a different name, and use it to compare against the repaired database
2) follow the rough instructions on my blog at CHECKDB From Every Angle: Using DBCC PAGE to find what repair will delete
Good luck.
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
December 2, 2008 at 7:02 pm
And whenever you want to post a 370+ line output file like this, please feel free to either trim it down some or post it as an attachment instead.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
December 2, 2008 at 7:17 pm
Thanks Paul, for the note. We figured as much on the outcome, just wanted some confirmation. I'll try your tips from the blog to try and see what we can see. Will also restore the corrupted DB and run a compare as you suggested.
RBarry, my apologies for the poor etiquette. I wanted to include all the errors in case someone might have seen something that could have helped. An attachment would have been a much wiser approach.
Thanks again to you both.
December 2, 2008 at 8:37 pm
First run completed. Received new errors
---
Server: Msg 8976, Level 16, State 1, Line 2
Table error: Object ID 1794105432, index ID 1. Page (7:143180) was not seen in the scan although its parent (7:501091) and previous (7:143179) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 2
Table error: Object ID 1794105432, index ID 1. Page (7:143181) is missing a reference from previous page (7:143180). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 2
---
Hoping that rerunning the process wraps up the rest as we ony received 30 consistency errors after this first go. I assume it is not uncommon to have to run it a few time before the DB stops kick out errors or does someone see something here that will prevent a complete cleanup?
Thanks.
December 2, 2008 at 8:51 pm
It could be one of two things:
1) some corruptions prevent CHECKDB from being able to check all parts of a structure, so when they're fixed CHECKDB may discover new corruptions
2) the repairs rebuilt some indexes (which they will in your case) and the I/O subsystem is corrupt enough that the new indexes are becoming corrupt as they're built
In your case, I suspect #2, but I could be wrong.
Thanks
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
December 3, 2008 at 12:05 am
rbarryyoung (12/2/2008)
And whenever you want to post a 370+ line output file like this, please feel free to either trim it down some or post it as an attachment instead.
For checkDB output, I'd recommend attach, not trim. Trimming the output may mean that a critical message gets omitted.
jwbrown: Running CheckDB with the no_infomsgs option will leave out all of those x rows in y pages messages. Have you checked the system event log and any SAN logs that you have to see if you're getting any errors or warnings?
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
December 3, 2008 at 3:44 am
2nd pass took 4 hours, 1st was 3.5.
Delighted to find that the 30 remaining consistency errors were found and fixed on the 2nd pass.
We seem to be operable again.
Thanks again everyone.
December 3, 2008 at 4:46 am
jwbrown65 (12/3/2008)
We seem to be operable again.Thanks again everyone.
Great.
If I may suggest...
Evaluate your backup strategy in light of this event.
Set up a job to run checkdb (without any of the repair options, just no_infomsgs and all_errormsgs) on a regular basis. Weekly's good to start with.
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
December 3, 2008 at 7:02 am
jwbrown65 (12/3/2008)
2nd pass took 4 hours, 1st was 3.5.Delighted to find that the 30 remaining consistency errors were found and fixed on the 2nd pass.
We seem to be operable again.
Thanks again everyone.
Ok - so it was #1 in my list above - that's better than #2. Please follow Gail's advice in the post above so next time you don't have to lose data.
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply