December 11, 2007 at 4:15 am
I am hoping that someone might be able to suggest what next step I should take to minimise any impact on the database having recieved the following error?
We received the following error from our database:
HP OpenView Operations for Windows sent you following message as an e-mail:
EventID: 0x4000429C (17052) - Error: 8908, Severity: 22, State: 6
Table error: Database ID 7, object ID 1575168857, index ID 0. Chain linkage mismatch. (1:5193938)->next = (1:5193939), but (1:5193939)->prev = (1:5193940).
On running DBCC CHECKDB(database) WITH NO_INFOMSGS, ALL_ERRORMSGS here is the output:
Server: Msg 2534, Level 16, State 2, Line 1
Table error: Page (1:5193939) with object ID 1575168857, index ID 0 in its header is allocated by another object.
Server: Msg 2534, Level 16, State 1, Line 1
Table error: Page (1:5193940) with object ID 1575168857, index ID 0 in its header is allocated by another object.
Server: Msg 2534, Level 16, State 1, Line 1
Table error: Page (1:5193941) with object ID 1575168857, index ID 0 in its header is allocated by another object.
Server: Msg 2534, Level 16, State 1, Line 1
Table error: Page (1:5193942) with object ID 1575168857, index ID 0 in its header is allocated by another object.
Server: Msg 2534, Level 16, State 1, Line 1
Table error: Page (1:5193943) with object ID 1575168857, index ID 0 in its header is allocated by another object.
Server: Msg 2534, Level 16, State 1, Line 1
Table error: Page (1:5862611) with object ID 1575168857, index ID 0 in its header is allocated by another object.
Server: Msg 2534, Level 16, State 1, Line 1
Table error: Page (1:5862612) with object ID 1575168857, index ID 0 in its header is allocated by another object.
Server: Msg 2534, Level 16, State 1, Line 1
Table error: Page (1:5862613) with object ID 1575168857, index ID 0 in its header is allocated by another object.
Server: Msg 2534, Level 16, State 1, Line 1
Table error: Page (1:5862614) with object ID 1575168857, index ID 0 in its header is allocated by another object.
Server: Msg 2534, Level 16, State 1, Line 1
Table error: Page (1:5862615) with object ID 1575168857, index ID 0 in its header is allocated by another object.
Server: Msg 2534, Level 16, State 1, Line 1
Table error: Page (1:9193438) with object ID 1575168857, index ID 0 in its header is allocated by another object.
Server: Msg 2534, Level 16, State 1, Line 1
Table error: Page (1:9193439) with object ID 1575168857, index ID 0 in its header is allocated by another object.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 1. Page (1:5193943) is missing a reference from previous page (1:5200688). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 1. Page (1:5862615) is missing a reference from previous page (1:5869480). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 1. Page (1:9193438) is missing a reference from previous page (1:8709748). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 1. Page (1:9193439) is missing a reference from previous page (1:8709938). Possible chain linkage problem.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:5193082), slot 89, in object ID 1575168857, index ID 6, refers to page (1:5193939), slot 0, in object ID 1575168857, index ID 1.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:5193082), slot 90, in object ID 1575168857, index ID 6, refers to page (1:5193940), slot 0, in object ID 1575168857, index ID 1.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:5193082), slot 91, in object ID 1575168857, index ID 6, refers to page (1:5193941), slot 0, in object ID 1575168857, index ID 1.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:5193082), slot 92, in object ID 1575168857, index ID 6, refers to page (1:5193942), slot 0, in object ID 1575168857, index ID 1.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:5193082), slot 93, in object ID 1575168857, index ID 6, refers to page (1:5193943), slot 0, in object ID 1575168857, index ID 1.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1575168857, index ID 6: Page (1:5193938) could not be processed. See other errors for details.
Server: Msg 8941, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 6, page (1:5193938). Test (sorted .offset >= PAGEHEADSIZE) failed. Slot 293, offset 0x1 is invalid.
Server: Msg 8942, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 6, page (1:5193938). Test (sorted.offset >= max) failed. Slot 0, offset 0x125 overlaps with the prior row.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 6. Page (1:5193938) was not seen in the scan although its parent (1:5193082) and previous (1:5193937) refer to it. Check any previous errors.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:5193939) allocated to object ID 1575168857, index ID 6 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:5193940) allocated to object ID 1575168857, index ID 6 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:5193941) allocated to object ID 1575168857, index ID 6 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:5193942) allocated to object ID 1575168857, index ID 6 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:5193943) allocated to object ID 1575168857, index ID 6 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 6. Page (1:5199784) is missing a reference from previous page (1:5193943). Possible chain linkage problem.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:5862540), slot 39, in object ID 1575168857, index ID 6, refers to page (1:5862611), slot 0, in object ID 1575168857, index ID 1.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:5862540), slot 40, in object ID 1575168857, index ID 6, refers to page (1:5862612), slot 0, in object ID 1575168857, index ID 1.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:5862540), slot 41, in object ID 1575168857, index ID 6, refers to page (1:5862613), slot 0, in object ID 1575168857, index ID 1.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:5862540), slot 42, in object ID 1575168857, index ID 6, refers to page (1:5862614), slot 0, in object ID 1575168857, index ID 1.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:5862540), slot 43, in object ID 1575168857, index ID 6, refers to page (1:5862615), slot 0, in object ID 1575168857, index ID 1.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1575168857, index ID 6: Page (1:5862610) could not be processed. See other errors for details.
Server: Msg 8941, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 6, page (1:5862610). Test (sorted .offset >= PAGEHEADSIZE) failed. Slot 229, offset 0x1 is invalid.
Server: Msg 8942, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 6, page (1:5862610). Test (sorted.offset >= max) failed. Slot 0, offset 0xe5 overlaps with the prior row.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 6. Page (1:5862610) was not seen in the scan although its parent (1:5862540) and previous (1:5862609) refer to it. Check any previous errors.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:5862611) allocated to object ID 1575168857, index ID 6 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:5862612) allocated to object ID 1575168857, index ID 6 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:5862613) allocated to object ID 1575168857, index ID 6 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:5862614) allocated to object ID 1575168857, index ID 6 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:5862615) allocated to object ID 1575168857, index ID 6 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 6. Page (1:5869512) is missing a reference from previous page (1:5862615). Possible chain linkage problem.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:9136339) allocated to object ID 1575168857, index ID 7 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 7. Page (1:9136339) was not seen in the scan although its parent (1:15732026) and previous (1:9136338) refer to it. Check any previous errors.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:9136340) allocated to object ID 1575168857, index ID 7 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 7. Index node page (1:15732026), slot 106 refers to child page (1:9136340) and previous child (1:9136339), but they were not encountered.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:9136341) allocated to object ID 1575168857, index ID 7 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 7. Index node page (1:15732026), slot 107 refers to child page (1:9136341) and previous child (1:9136340), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 7. Page (1:9136342) is missing a reference from previous page (1:9136341). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1575168857, index ID 7: Page (1:9193437) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 7, page (1:9193437). 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 1575168857, index ID 7. Page (1:9193437) was not seen in the scan although its parent (1:15544515) and previous (1:9193436) refer to it. Check any previous errors.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:9193438) allocated to object ID 1575168857, index ID 7 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:9193439) allocated to object ID 1575168857, index ID 7 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 7. Page (1:9197088) is missing a reference from previous page (1:9193439). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1575168857, index ID 7: Page (1:9779386) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 7, page (1:9779386). 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 1575168857, index ID 7. Page (1:9779386) was not seen in the scan although its parent (1:10224195) and previous (1:9779385) refer to it. Check any previous errors.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:9779387) allocated to object ID 1575168857, index ID 7 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 7. Index node page (1:10224195), slot 88 refers to child page (1:9779387) and previous child (1:9779386), but they were not encountered.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:9779388) allocated to object ID 1575168857, index ID 7 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 7. Index node page (1:10224195), slot 89 refers to child page (1:9779388) and previous child (1:9779387), but they were not encountered.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:9779389) allocated to object ID 1575168857, index ID 7 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 7. Index node page (1:10224195), slot 90 refers to child page (1:9779389) and previous child (1:9779388), but they were not encountered.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:9779390) allocated to object ID 1575168857, index ID 7 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 7. Index node page (1:10224195), slot 91 refers to child page (1:9779390) and previous child (1:9779389), but they were not encountered.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:9779391) allocated to object ID 1575168857, index ID 7 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 7. Index node page (1:10224195), slot 92 refers to child page (1:9779391) and previous child (1:9779390), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1575168857, index ID 7. Page (1:9919920) is missing a reference from previous page (1:9779391). Possible chain linkage problem.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:15544515), slot 72, in object ID 1575168857, index ID 7, refers to page (1:9193438), slot 0, in object ID 1575168857, index ID 1.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:15544515), slot 73, in object ID 1575168857, index ID 7, refers to page (1:9193439), slot 0, in object ID 1575168857, index ID 1.
CHECKDB found 0 allocation errors and 75 consistency errors in table 'f_analogvalues' (object ID 1575168857).
CHECKDB found 0 allocation errors and 75 consistency errors in database 'DATABASE'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (DATABASE ).
December 11, 2007 at 12:01 pm
You've got a bunch of corruption.
You have two options for getting rid of it:
1) restore from your backups
2) run REPAIR_ALLOW_DATA_LOSS
#1 is by far the preferred option as you will minimize data loss. #2 will cause data loss and any business logic you have inherent in the database will be broken.
Whichever you choose, make sure you do root-cause analysis to figure out what happened - most likely an issue with the IO subsystem.
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 14, 2007 at 3:20 am
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply