SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Database Corruption


Database Corruption

Author
Message
Sammy Balls
Sammy Balls
SSC-Enthusiastic
SSC-Enthusiastic (170 reputation)SSC-Enthusiastic (170 reputation)SSC-Enthusiastic (170 reputation)SSC-Enthusiastic (170 reputation)SSC-Enthusiastic (170 reputation)SSC-Enthusiastic (170 reputation)SSC-Enthusiastic (170 reputation)SSC-Enthusiastic (170 reputation)

Group: General Forum Members
Points: 170 Visits: 43
When I run DBCC CheckDB i get erroros. the thing that i saw is corruption in sys.sysobjvalues in addition to other tables. attached is the result of DBCC CheckDb



DBCC CheckDB ('medmas') WITH NO_INFOMSGS, ALL_ERRORMSGS

Msg 8948, Level 16, State 3, Line 6
Database error: Page (1:6092) is marked with the wrong type in PFS page (1:1). PFS status 0x70 expected 0x60.
Msg 8906, Level 16, State 1, Line 6
Page (1:6092) in database ID 7 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 8906, Level 16, State 1, Line 6
Page (1:6125) in database ID 7 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 8906, Level 16, State 1, Line 6
Page (1:6126) in database ID 7 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 8905, Level 16, State 1, Line 6
Extent (1:1769264) in database ID 7 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
CHECKDB found 5 allocation errors and 0 consistency errors not associated with any single object.
Msg 8961, Level 16, State 2, Line 6
Table error: Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). The off-row data node at page (1:10088), slot 0, text ID 1320419328 does not match its reference from page (1:571822), slot 0.
Msg 8961, Level 16, State 2, Line 6
Table error: Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). The off-row data node at page (1:46354), slot 0, text ID 1109065728 does not match its reference from page (1:3608760), slot 1.
Msg 8961, Level 16, State 2, Line 6
Table error: Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). The off-row data node at page (1:48066), slot 0, text ID 1808072704 does not match its reference from page (1:3608760), slot 2.
Msg 8961, Level 16, State 2, Line 6
Table error: Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). The off-row data node at page (1:48067), slot 0, text ID 618332160 does not match its reference from page (1:3608760), slot 3.
Msg 8961, Level 16, State 2, Line 6
Table error: Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). The off-row data node at page (1:175467), slot 0, text ID 1864892416 does not match its reference from page (1:5603002), slot 2.
Msg 8961, Level 16, State 2, Line 6
Table error: Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). The off-row data node at page (1:554941), slot 0, text ID 618332160 does not match its reference from page (1:48067), slot 0.
Msg 8961, Level 16, State 2, Line 6
Table error: Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). The off-row data node at page (1:571810), slot 3, text ID 753401856 does not match its reference from page (1:5603002), slot 6.
Msg 8961, Level 16, State 2, Line 6
Table error: Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). The off-row data node at page (1:571822), slot 0, text ID 1320419328 does not match its reference from page (1:5603002), slot 4.
Msg 8961, Level 16, State 2, Line 6
Table error: Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). The off-row data node at page (1:1779339), slot 0, text ID 1828847616 does not match its reference from page (1:31167), slot 2.
Msg 8961, Level 16, State 2, Line 6
Table error: Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). The off-row data node at page (1:2561146), slot 0, text ID 1193213952 does not match its reference from page (1:5603002), slot 3.
Msg 8929, Level 16, State 1, Line 6
Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 281474980642816 (type In-row data): Errors found in off-row data with ID 1828847616 owned by data record identified by RID = (1:31167:2)
Msg 8929, Level 16, State 1, Line 6
Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 281474980642816 (type In-row data): Errors found in off-row data with ID 1109065728 owned by data record identified by RID = (1:3608760:1)
Msg 8929, Level 16, State 1, Line 6
Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 281474980642816 (type In-row data): Errors found in off-row data with ID 1808072704 owned by data record identified by RID = (1:3608760:2)
Msg 8929, Level 16, State 1, Line 6
Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 281474980642816 (type In-row data): Errors found in off-row data with ID 618332160 owned by data record identified by RID = (1:3608760:3)
Msg 8929, Level 16, State 1, Line 6
Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 281474980642816 (type In-row data): Errors found in off-row data with ID 1864892416 owned by data record identified by RID = (1:5603002:2)
Msg 8929, Level 16, State 1, Line 6
Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 281474980642816 (type In-row data): Errors found in off-row data with ID 1193213952 owned by data record identified by RID = (1:5603002:3)
Msg 8929, Level 16, State 1, Line 6
Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 281474980642816 (type In-row data): Errors found in off-row data with ID 1320419328 owned by data record identified by RID = (1:5603002:4)
Msg 8929, Level 16, State 1, Line 6
Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 281474980642816 (type In-row data): Errors found in off-row data with ID 753401856 owned by data record identified by RID = (1:5603002:6)
CHECKDB found 0 allocation errors and 18 consistency errors in table 'sys.sysobjvalues' (object ID 60).
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1769232) allocated to object ID 177188177, index ID 3, partition ID 72057610686496768, alloc unit ID 72057610737483776 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1769233) allocated to object ID 177188177, index ID 3, partition ID 72057610686496768, alloc unit ID 72057610737483776 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1769234) allocated to object ID 177188177, index ID 3, partition ID 72057610686496768, alloc unit ID 72057610737483776 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1769235) allocated to object ID 177188177, index ID 3, partition ID 72057610686496768, alloc unit ID 72057610737483776 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1767364) allocated to object ID 177188177, index ID 6, partition ID 72057610686431232, alloc unit ID 72057610737418240 (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 6
Table error: Object ID 177188177, index ID 6, partition ID 72057610686431232, alloc unit ID 72057610737418240 (type In-row data). Page (1:1767364) was not seen in the scan although its parent (1:9903760) and previous (1:9903796) refer to it. Check any previous errors.
Msg 8978, Level 16, State 1, Line 6
Table error: Object ID 177188177, index ID 6, partition ID 72057610686431232, alloc unit ID 72057610737418240 (type In-row data). Page (1:1767366) is missing a reference from previous page (1:9903809). Possible chain linkage problem.
Msg 8976, Level 16, State 1, Line 6
Table error: Object ID 177188177, index ID 3, partition ID 72057610686496768, alloc unit ID 72057610737483776 (type In-row data). Page (1:1769232) was not seen in the scan although its parent (1:9917633) and previous (1:9917987) refer to it. Check any previous errors.
Msg 8980, Level 16, State 1, Line 6
Table error: Object ID 177188177, index ID 3, partition ID 72057610686496768, alloc unit ID 72057610737483776 (type In-row data). Index node page (1:9917633), slot 246 refers to child page (1:1769233) and previous child (1:9918101), but they were not encountered.
Msg 8980, Level 16, State 1, Line 6
Table error: Object ID 177188177, index ID 3, partition ID 72057610686496768, alloc unit ID 72057610737483776 (type In-row data). Index node page (1:9928414), slot 275 refers to child page (1:1769234) and previous child (1:9920618), but they were not encountered.
Msg 8976, Level 16, State 1, Line 6
Table error: Object ID 177188177, index ID 3, partition ID 72057610686496768, alloc unit ID 72057610737483776 (type In-row data). Page (1:1769235) was not seen in the scan although its parent (1:1565098) and previous (1:9928179) refer to it. Check any previous errors.
Msg 8978, Level 16, State 1, Line 6
Table error: Object ID 177188177, index ID 6, partition ID 72057610686431232, alloc unit ID 72057610737418240 (type In-row data). Page (1:9903797) is missing a reference from previous page (1:1767364). Possible chain linkage problem.
Msg 8935, Level 16, State 1, Line 6
Table error: Object ID 177188177, index ID 6, partition ID 72057610686431232, alloc unit ID 72057610737418240 (type In-row data). The previous link (1:9903809) on page (1:9903810) does not match the previous page (1:1767366) that the parent (1:9903760), slot 62 expects for this page.
Msg 8978, Level 16, State 1, Line 6
Table error: Object ID 177188177, index ID 3, partition ID 72057610686496768, alloc unit ID 72057610737483776 (type In-row data). Page (1:9917988) is missing a reference from previous page (1:1769232). Possible chain linkage problem.
Msg 8935, Level 16, State 1, Line 6
Table error: Object ID 177188177, index ID 3, partition ID 72057610686496768, alloc unit ID 72057610737483776 (type In-row data). The previous link (1:9918101) on page (1:9918102) does not match the previous page (1:1769233) that the parent (1:9917633), slot 247 expects for this page.
Msg 8935, Level 16, State 1, Line 6
Table error: Object ID 177188177, index ID 3, partition ID 72057610686496768, alloc unit ID 72057610737483776 (type In-row data). The previous link (1:9920618) on page (1:9920619) does not match the previous page (1:1769234) that the parent (1:9928414), slot 276 expects for this page.
Msg 8978, Level 16, State 1, Line 6
Table error: Object ID 177188177, index ID 3, partition ID 72057610686496768, alloc unit ID 72057610737483776 (type In-row data). Page (1:9928180) is missing a reference from previous page (1:1769235). Possible chain linkage problem.
CHECKDB found 0 allocation errors and 17 consistency errors in table 'MedicationRxAudit_ORG' (object ID 177188177).
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1767244) allocated to object ID 417189032, index ID 1, partition ID 72057610757079040, alloc unit ID 72057603701932032 (type LOB data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1767245) allocated to object ID 417189032, index ID 1, partition ID 72057610757079040, alloc unit ID 72057603701932032 (type LOB data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1767246) allocated to object ID 417189032, index ID 1, partition ID 72057610757079040, alloc unit ID 72057603701932032 (type LOB data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1767247) allocated to object ID 417189032, index ID 1, partition ID 72057610757079040, alloc unit ID 72057603701932032 (type LOB data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 8965, Level 16, State 1, Line 6
Table error: Object ID 417189032, index ID 1, partition ID 72057610757079040, alloc unit ID 72057603701932032 (type LOB data). The off-row data node at page (1:1767244), slot 0, text ID 2082865152 is referenced by page (1:1685072), slot 54, but was not seen in the scan.
Msg 8965, Level 16, State 1, Line 6
Table error: Object ID 417189032, index ID 1, partition ID 72057610757079040, alloc unit ID 72057603701932032 (type LOB data). The off-row data node at page (1:1767245), slot 0, text ID 2082865152 is referenced by page (1:1685072), slot 54, but was not seen in the scan.
Msg 8965, Level 16, State 1, Line 6
Table error: Object ID 417189032, index ID 1, partition ID 72057610757079040, alloc unit ID 72057603701932032 (type LOB data). The off-row data node at page (1:1767246), slot 0, text ID 2082865152 is referenced by page (1:1685072), slot 54, but was not seen in the scan.
Msg 8965, Level 16, State 1, Line 6
Table error: Object ID 417189032, index ID 1, partition ID 72057610757079040, alloc unit ID 72057603701932032 (type LOB data). The off-row data node at page (1:1767247), slot 0, text ID 2082865152 is referenced by page (1:1685072), slot 54, but was not seen in the scan.
Msg 8929, Level 16, State 1, Line 6
Object ID 417189032, index ID 1, partition ID 72057610757079040, alloc unit ID 72057610809180160 (type In-row data): Errors found in off-row data with ID 2082865152 owned by data record identified by RID = (1:1685072:54)
CHECKDB found 0 allocation errors and 9 consistency errors in table 'MedicationRxDocument_ORG' (object ID 417189032).
Msg 8961, Level 16, State 1, Line 6
Table error: Object ID 565889383, index ID 1, partition ID 72057610661527552, alloc unit ID 71813205187821568 (type LOB data). The off-row data node at page (1:5432612), slot 37, text ID 15169068859392 does not match its reference from page (1:6046140), slot 29.
Msg 8961, Level 16, State 1, Line 6
Table error: Object ID 565889383, index ID 1, partition ID 72057610661527552, alloc unit ID 71813205187821568 (type LOB data). The off-row data node at page (1:5432612), slot 39, text ID 15169068924928 does not match its reference from page (1:6046140), slot 30.
Msg 8961, Level 16, State 1, Line 6
Table error: Object ID 565889383, index ID 1, partition ID 72057610661527552, alloc unit ID 71813205187821568 (type LOB data). The off-row data node at page (1:5432612), slot 41, text ID 15169068990464 does not match its reference from page (1:6046140), slot 31.
Msg 8929, Level 16, State 1, Line 6
Object ID 565889383, index ID 1, partition ID 72057610661527552, alloc unit ID 72057610712186880 (type In-row data): Errors found in off-row data with ID 15075770302464 owned by data record identified by RID = (1:6046140:29)
Msg 8929, Level 16, State 1, Line 6
Object ID 565889383, index ID 1, partition ID 72057610661527552, alloc unit ID 72057610712186880 (type In-row data): Errors found in off-row data with ID 15075770368000 owned by data record identified by RID = (1:6046140:30)
Msg 8929, Level 16, State 1, Line 6
Object ID 565889383, index ID 1, partition ID 72057610661527552, alloc unit ID 72057610712186880 (type In-row data): Errors found in off-row data with ID 15075770433536 owned by data record identified by RID = (1:6046140:31)
CHECKDB found 0 allocation errors and 6 consistency errors in table 'ECTPROCEDUREDETAIL_ORG' (object ID 565889383).
Msg 2575, Level 16, State 1, Line 6
The Index Allocation Map (IAM) page (1:6092) is pointed to by the next pointer of IAM page (1:5345367) in object ID 597889497, index ID 1, partition ID 72057610661593088, alloc unit ID 72057610712252416 (type In-row data), but it was not detected in the scan.
Msg 8946, Level 16, State 3, Line 6
Table error: Allocation page (1:6092) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.
Msg 8946, Level 16, State 3, Line 6
Table error: Allocation page (1:6092) has invalid IAM_PAGE page header values. Type is 1. Check type, alloc unit ID and page ID on the page.
Msg 7965, Level 16, State 2, Line 6
Table error: Could not check object ID 597889497, index ID 1, partition ID 72057610661593088, alloc unit ID 72057610712252416 (type In-row data) due to invalid allocation (IAM) page(s).
CHECKDB found 1 allocation errors and 3 consistency errors in table 'ECTPROCEDUREDETAIL_AUDIT_ORG' (object ID 597889497).
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1761877) allocated to object ID 977191027, index ID 1, partition ID 72057610686627840, alloc unit ID 72057610737614848 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 8980, Level 16, State 1, Line 6
Table error: Object ID 977191027, index ID 1, partition ID 72057610686627840, alloc unit ID 72057610737614848 (type In-row data). Index node page (1:9928472), slot 121 refers to child page (1:1761877) and previous child (1:9928556), but they were not encountered.
Msg 8935, Level 16, State 1, Line 6
Table error: Object ID 977191027, index ID 1, partition ID 72057610686627840, alloc unit ID 72057610737614848 (type In-row data). The previous link (1:9928556) on page (1:9928557) does not match the previous page (1:1761877) that the parent (1:9928472), slot 122 expects for this page.
CHECKDB found 0 allocation errors and 3 consistency errors in table 'MedicationRxBilling_ORG' (object ID 977191027).
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1766253) allocated to object ID 1057191312, index ID 2, partition ID 72057610687676416, alloc unit ID 72057610738860032 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 8980, Level 16, State 1, Line 6
Table error: Object ID 1057191312, index ID 2, partition ID 72057610687676416, alloc unit ID 72057610738860032 (type In-row data). Index node page (1:9961168), slot 261 refers to child page (1:1766253) and previous child (1:9961307), but they were not encountered.
Msg 8935, Level 16, State 1, Line 6
Table error: Object ID 1057191312, index ID 2, partition ID 72057610687676416, alloc unit ID 72057610738860032 (type In-row data). The previous link (1:9961307) on page (1:9961308) does not match the previous page (1:1766253) that the parent (1:9961168), slot 262 expects for this page.
CHECKDB found 0 allocation errors and 3 consistency errors in table 'MedicationRxInteractionAudit_ORG' (object ID 1057191312).
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1768879) allocated to object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1769016) allocated to object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1769017) allocated to object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1769018) allocated to object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1769019) allocated to object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1769020) allocated to object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1769021) allocated to object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1769022) allocated to object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1769023) allocated to object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1769400) allocated to object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1769401) allocated to object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1769402) allocated to object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1769403) allocated to object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1769404) allocated to object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1769405) allocated to object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:1769406) allocated to object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 8980, Level 16, State 1, Line 6
Table error: Object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data). Index node page (1:1771954), slot 188 refers to child page (1:1768879) and previous child (1:1768878), but they were not encountered.
Msg 8980, Level 16, State 1, Line 6
Table error: Object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data). Index node page (1:1771954), slot 189 refers to child page (1:1769016) and previous child (1:1768879), but they were not encountered.
Msg 8980, Level 16, State 1, Line 6
Table error: Object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data). Index node page (1:1771954), slot 190 refers to child page (1:1769017) and previous child (1:1769016), but they were not encountered.
Msg 8980, Level 16, State 1, Line 6
Table error: Object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data). Index node page (1:1771954), slot 191 refers to child page (1:1769018) and previous child (1:1769017), but they were not encountered.
Msg 8980, Level 16, State 1, Line 6
Table error: Object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data). Index node page (1:1771954), slot 192 refers to child page (1:1769019) and previous child (1:1769018), but they were not encountered.
Msg 8980, Level 16, State 1, Line 6
Table error: Object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data). Index node page (1:1771954), slot 193 refers to child page (1:1769020) and previous child (1:1769019), but they were not encountered.
Msg 8980, Level 16, State 1, Line 6
Table error: Object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data). Index node page (1:1771954), slot 194 refers to child page (1:1769021) and previous child (1:1769020), but they were not encountered.
Msg 8980, Level 16, State 1, Line 6
Table error: Object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data). Index node page (1:1771954), slot 195 refers to child page (1:1769022) and previous child (1:1769021), but they were not encountered.
Msg 8980, Level 16, State 1, Line 6
Table error: Object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data). Index node page (1:1771954), slot 196 refers to child page (1:1769023) and previous child (1:1769022), but they were not encountered.
Msg 8980, Level 16, State 1, Line 6
Table error: Object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data). Index node page (1:1771954), slot 197 refers to child page (1:1769400) and previous child (1:1769023), but they were not encountered.
Msg 8980, Level 16, State 1, Line 6
Table error: Object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data). Index node page (1:1771954), slot 198 refers to child page (1:1769401) and previous child (1:1769400), but they were not encountered.
Msg 8980, Level 16, State 1, Line 6
Table error: Object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data). Index node page (1:1771954), slot 199 refers to child page (1:1769402) and previous child (1:1769401), but they were not encountered.
Msg 8980, Level 16, State 1, Line 6
Table error: Object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data). Index node page (1:1771954), slot 200 refers to child page (1:1769403) and previous child (1:1769402), but they were not encountered.
Msg 8980, Level 16, State 1, Line 6
Table error: Object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data). Index node page (1:1771954), slot 201 refers to child page (1:1769404) and previous child (1:1769403), but they were not encountered.
Msg 8980, Level 16, State 1, Line 6
Table error: Object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data). Index node page (1:1771954), slot 202 refers to child page (1:1769405) and previous child (1:1769404), but they were not encountered.
Msg 8980, Level 16, State 1, Line 6
Table error: Object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data). Index node page (1:1771954), slot 203 refers to child page (1:1769406) and previous child (1:1769405), but they were not encountered.
Msg 8978, Level 16, State 1, Line 6
Table error: Object ID 1446400322, index ID 1, partition ID 72057610645995520, alloc unit ID 72057610696327168 (type In-row data). Page (1:1769407) is missing a reference from previous page (1:1769406). Possible chain linkage problem.
CHECKDB found 0 allocation errors and 33 consistency errors in table 'AUDIT_EVENT_LOG_ORG' (object ID 1446400322).
Msg 2533, Level 16, State 1, Line 6
Table error: page (1:6124) allocated to object ID 1695501269, index ID 2, partition ID 72057610696916992, alloc unit ID 72057610748559360 (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 6
Table error: Object ID 1695501269, index ID 2, partition ID 72057610696916992, alloc unit ID 72057610748559360 (type In-row data). Page (1:6124) was not seen in the scan although its parent (1:45624) and previous (1:46204) refer to it. Check any previous errors.
Msg 8935, Level 16, State 1, Line 6
Table error: Object ID 1695501269, index ID 2, partition ID 72057610696916992, alloc unit ID 72057610748559360 (type In-row data). The previous link (1:46204) on page (1:46205) does not match the previous page (1:6124) that the parent (1:45624), slot 241 expects for this page.
Msg 8978, Level 16, State 1, Line 6
Table error: Object ID 1695501269, index ID 2, partition ID 72057610696916992, alloc unit ID 72057610748559360 (type In-row data). Page (1:46205) is missing a reference from previous page (1:46204). Possible chain linkage problem.
CHECKDB found 0 allocation errors and 4 consistency errors in table 'ORDERS_DETAIL_ORG' (object ID 1695501269).
Msg 8951, Level 16, State 1, Line 6
Table error: table 'MedicationRxMeasure_ORG' (ID 2017012004). Data row does not have a matching index row in the index 'IX_MedicationRxMeasure' (ID 12). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 6
Data row (1:5439682:52) identified by (HEAP RID = (1:5439682:52)) with index values 'MedID = 221103 and HEAP RID = (1:5439682:52)'.
CHECKDB found 0 allocation errors and 1 consistency errors in table 'MedicationRxMeasure_ORG' (object ID 2017012004).
CHECKDB found 6 allocation errors and 97 consistency errors in database 'MedMas'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (MedMas).
prettsons
prettsons
SSCarpal Tunnel
SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)

Group: General Forum Members
Points: 4399 Visits: 1475
Hi Sammy,

If you have updated backup, then restore from it. Otherwise, you can give a chance to DBCC CHECKDB Repair Allow Data Loss option but, remember one thing, in this case, you can lose your data.

You can also try a SQL database repair tool to repair your corrupt database. Download the software and install it.

Note: The demo version of this software shows the preview of recoverable data.

Good Luck!

SQL Database Recovery Expert :-)
John Walker
John Walker
SSCertifiable
SSCertifiable (5.4K reputation)SSCertifiable (5.4K reputation)SSCertifiable (5.4K reputation)SSCertifiable (5.4K reputation)SSCertifiable (5.4K reputation)SSCertifiable (5.4K reputation)SSCertifiable (5.4K reputation)SSCertifiable (5.4K reputation)

Group: General Forum Members
Points: 5430 Visits: 293
> Detach SQL Server database and move your MDF to save location.
> Create new databse of same name, same files, same file location and same file size.
> Now Stop SQL server.
> Swap MDF file of just created database to your save one.
> Then Start SQL Server

Now database will go to suspect mode

> Execute the following query to set database to emergency mode and single user mode
ALTER DATABSE <db name> SET EMERGENCY
ALTER DATABASE <db name> SET SINGLE_USER


> Execute the below query to perform recovery
DBCC CHECKDB (<db name>, REPAIR_ALLOW_DATA_LOSS)


> Now set database to multi user and online
ALTER DATABASE <db name> SET MULTI_USER
ALTER DATABSE <db name> SET ONLINE



This process will repair your corrupted database but you can also have some data lose. In such cause you can try SQL data recovery tool that can help you to repair your database and it's quite cheaper as well.
Eddie Wuerch
Eddie Wuerch
SSCertifiable
SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)

Group: General Forum Members
Points: 6351 Visits: 2549
All of this is absolutely terrible advice, and can only make a bad situation worse:

johnwalker10 (12/6/2016)
> Detach SQL Server database and move your MDF to save location.
> Create new databse of same name, same files, same file location and same file size.
> Now Stop SQL server.
> Swap MDF file of just created database to your save one.
> Then Start SQL Server

Now database will go to suspect mode


And it will also throw out the transaction log, which should instead be backed up and used to recover from a backup from before corruption.
This database is online; there is no need to discard the log and force data distruction.
Please do not take any of that advice. At this point you can still recover the data and the database, but those steps will prevent you from doing so.

Just glancing over the checkdb dump, this looks like disk-based corruption. If your transaction log and transaction log backups survived the event, then you can backup the log (with the NO_TRUNCATE option if things are damaged), and attempt to restore the database from backup, rolling forward and through the corruption. The changes caused by disk-based corruption are not written to the SQL Server transaction log, allowing you to replay all of your transactions on a non-damaged restore (again, provided the transaction log survived the event).

If you cannot recover from backup, then you can at least take a new backup of the damaged database (yes, you can back up and restore corrupted databases), and perform all of your DBCC repair work there to see how much gets deleted if you use a repair_allow_data_loss. It is also possible to try upgrading the corrupted database to a newer version of SQL Server (this works, too) that will use a newer version of the DBCC CHECK* tools.

Eddie Wuerch
MCM: SQL
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum







































































































































































SQLServerCentral


Search