x

Msg 8945, level 16 while running dbcc checktable

Hi,

I ran checkdb on the database but the result was as follows :

Msg 8951, Level 16, State 1, Line 6 Table error: table 'ProductFile' (ID 279672044). Data row does not have a matching index row in the index 'UQ_ProductFile' (ID 2). Possible missing or invalid keys for the index row matching: Msg 8955, Level 16, State 1, Line 6 Data row (1:2799552:191) identified by (ProductFile_Idn = 329339) with index values 'Product_Idn = 44966 and FileInfo_Idn = 597344 and ProductFile_Idn = 329339'. Msg 8951, Level 16, State 1, Line 6 Table error: table 'ProductFile' (ID 279672044). Data row does not have a matching index row in the index 'UQ_ProductFile' (ID 2). Possible missing or invalid keys for the index row matching: Msg 8955, Level 16, State 1, Line 6 Data row (1:2840824:229) identified by (ProductFile_Idn = 329656) with index values 'Product_Idn = 45034 and FileInfo_Idn = 595629 and ProductFile_Idn = 329656'. CHECKDB found 0 allocation errors and 2 consistency errors in table 'ProductFile' (object ID 279672044). Msg 8964, Level 16, State 1, Line 6 Table error: Object ID 306816155, index ID 1, partition ID 72057627735556096, alloc unit ID 72057594088980480 (type LOB data). The off-row data node at page (1:2236835), slot 9, text ID 570376912896 is not referenced. Msg 8964, Level 16, State 1, Line 6 Table error: Object ID 306816155, index ID 1, partition ID 72057627735556096, alloc unit ID 72057594088980480 (type LOB data). The off-row data node at page (1:2674512), slot 0, text ID 565904343040 is not referenced. CHECKDB found 0 allocation errors and 2 consistency errors in table 'DistributionTaskLog' (object ID 306816155). Msg 8981, Level 16, State 1, Line 6 Table error: Object ID 838294046, index ID 1, partition ID 72057624349966336, alloc unit ID 72057626471104512 (type In-row data). The next pointer of (1:2722660) refers to page (1:2191651). Neither (1:2191651) nor its parent were encountered. Possible bad chain linkage. Msg 8935, Level 16, State 1, Line 6 Table error: Object ID 838294046, index ID 1, partition ID 72057624349966336, alloc unit ID 72057626471104512 (type In-row data). The previous link (1:2862287) on page (1:2449593) does not match the previous page (1:2926352) that the parent (1:2511582), slot 99 expects for this page. Msg 8936, Level 16, State 1, Line 6 Table error: Object ID 838294046, index ID 1, partition ID 72057624349966336, alloc unit ID 72057626471104512 (type In-row data). B-tree chain linkage mismatch. (1:2926352)->next = (1:2449593), but (1:2449593)->Prev = (1:2862287). Msg 8935, Level 16, State 1, Line 6 Table error: Object ID 838294046, index ID 1, partition ID 72057624349966336, alloc unit ID 72057626471104512 (type In-row data). The previous link (1:2831272) on page (1:2589790) does not match the previous page (1:2840962) that the parent (1:2237962), slot 86 expects for this page. Msg 8936, Level 16, State 1, Line 6 Table error: Object ID 838294046, index ID 1, partition ID 72057624349966336, alloc unit ID 72057626471104512 (type In-row data). B-tree chain linkage mismatch. (1:2840962)->next = (1:2589790), but (1:2589790)->Prev = (1:2831272). Msg 8978, Level 16, State 1, Line 6 Table error: Object ID 838294046, index ID 1, partition ID 72057624349966336, alloc unit ID 72057626471104512 (type In-row data). Page (1:2840880) is missing a reference from previous page (1:2589790). Possible chain linkage problem. Msg 8935, Level 16, State 1, Line 6 Table error: Object ID 838294046, index ID 1, partition ID 72057624349966336, alloc unit ID 72057626471104512 (type In-row data). The previous link (1:2589789) on page (1:2840962) does not match the previous page (1:2722660) that the parent (1:2237962), slot 85 expects for this page. Msg 8978, Level 16, State 1, Line 6 Table error: Object ID 838294046, index ID 1, partition ID 72057624349966336, alloc unit ID 72057626471104512 (type In-row data). Page (1:2840962) is missing a reference from previous page (1:2589789). Possible chain linkage problem. Msg 8935, Level 16, State 1, Line 6 Table error: Object ID 838294046, index ID 1, partition ID 72057624349966336, alloc unit ID 72057626471104512 (type In-row data). The previous link (1:2449592) on page (1:2926352) does not match the previous page (1:2862287) that the parent (1:2511582), slot 98 expects for this page. Msg 8978, Level 16, State 1, Line 6 Table error: Object ID 838294046, index ID 1, partition ID 72057624349966336, alloc unit ID 72057626471104512 (type In-row data). Page (1:2926352) is missing a reference from previous page (1:2449592). Possible chain linkage problem. CHECKDB found 0 allocation errors and 10 consistency errors in table 'LDAPUserGroups' (object ID 838294046). Msg 8978, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). Page (1:1188053) is missing a reference from previous page (1:2404578). Possible chain linkage problem. Msg 8978, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). Page (1:2240253) is missing a reference from previous page (1:2597892). Possible chain linkage problem. Msg 8978, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). Page (1:2240255) is missing a reference from previous page (1:2407463). Possible chain linkage problem. Msg 8935, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). The previous link (1:2402695) on page (1:2400514) does not match the previous page (1:2402772) that the parent (1:2522501), slot 152 expects for this page. Msg 8978, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). Page (1:2400514) is missing a reference from previous page (1:2402695). Possible chain linkage problem. Msg 8935, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). The previous link (1:2402689) on page (1:2400578) does not match the previous page (1:2523572) that the parent (1:2522501), slot 150 expects for this page. Msg 8978, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). Page (1:2400578) is missing a reference from previous page (1:2402689). Possible chain linkage problem. Msg 8935, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). The previous link (1:2402689) on page (1:2400579) does not match the previous page (1:98730) that the parent (1:2597160), slot 113 expects for this page. Msg 8978, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). Page (1:2400579) is missing a reference from previous page (1:2402689). Possible chain linkage problem. Msg 8935, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). The previous link (1:2761223) on page (1:2402772) does not match the previous page (1:2400578) that the parent (1:2522501), slot 151 expects for this page. Msg 8978, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). Page (1:2402772) is missing a reference from previous page (1:2761223). Possible chain linkage problem. Msg 8978, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). Page (1:2419464) is missing a reference from previous page (1:2455545). Possible chain linkage problem. Msg 8935, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). The previous link (1:2457246) on page (1:2455545) does not match the previous page (1:2529297) that the parent (1:2597160), slot 155 expects for this page. Msg 8978, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). Page (1:2455545) is missing a reference from previous page (1:2457246). Possible chain linkage problem. Msg 8978, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). Page (1:2457240) is missing a reference from previous page (1:2402773). Possible chain linkage problem. Msg 8936, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). B-tree chain linkage mismatch. (1:2523572)->next = (1:2465012), but (1:2465012)->Prev = (1:2400514). Msg 8935, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). The previous link (1:98730) on page (1:2527553) does not match the previous page (1:2400579) that the parent (1:2597160), slot 114 expects for this page. Msg 8935, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). The previous link (1:4700346) on page (1:2529297) does not match the previous page (1:2851787) that the parent (1:2597160), slot 154 expects for this page. Msg 8935, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). The previous link (1:2529297) on page (1:2536614) does not match the previous page (1:2419464) that the parent (1:2597160), slot 157 expects for this page. Msg 8981, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). The next pointer of (1:2851787) refers to page (1:2538755). Neither (1:2538755) nor its parent were encountered. Possible bad chain linkage. Msg 8981, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). The next pointer of (1:2597892) refers to page (1:2598147). Neither (1:2598147) nor its parent were encountered. Possible bad chain linkage. Msg 8935, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). The previous link (1:2527552) on page (1:2851787) does not match the previous page (1:4700346) that the parent (1:2597160), slot 153 expects for this page. Msg 8978, Level 16, State 1, Line 6 Table error: Object ID 1957582012, index ID 1, partition ID 72057624425660416, alloc unit ID 72057626550403072 (type In-row data). Page (1:2851787) is missing a reference from previous page (1:2527552). Possible chain linkage problem. CHECKDB found 0 allocation errors and 23 consistency errors in table 'TrustedItem' (object ID 1957582012). Msg 8906, Level 16, State 1, Line 6 Page (1:1175748) in database ID 5 is allocated in the SGAM (1:1022465) and PFS (1:1172760), 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:1189300) in database ID 5 is allocated in the SGAM (1:1022465) and PFS (1:1188936), 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:1442219) in database ID 5 is allocated in the SGAM (1:1022465) and PFS (1:1439664), 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:1442223) in database ID 5 is allocated in the SGAM (1:1022465) and PFS (1:1439664), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'. CHECKDB found 4 allocation errors and 0 consistency errors in table 'Vulnerability2' (object ID 2130822653). CHECKDB found 4 allocation errors and 37 consistency errors in database 'LDDB2012_test'. repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (LDDB2012_test).


In order to fix the same, I targetted each table in question and ran checktable but found the below reported :

Msg 1505, Level 16, State 1, Line 3 The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.TrustedItem' and the index name 'XPKTrustedItem'. The duplicate key value is (5308, 603552). Msg 1505, Level 16, State 1, Line 3 The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.TrustedItem' and the index name 'XIFTrustedItemId'. The duplicate key value is (603552, 5308). DBCC results for 'TrustedItem'. Msg 8945, Level 16, State 1, Line 3 Table error: Object ID 1957582012, index ID 1 will be rebuilt. Could not repair this error. Msg 8945, Level 16, State 1, Line 3 Table error: Object ID 1957582012, index ID 2 will be rebuilt. Could not repair this error. There are 178268 rows in 5042 pages for object "TrustedItem". CHECKTABLE found 0 allocation errors and 23 consistency errors in table 'TrustedItem' (object ID 1957582012). CHECKTABLE fixed 0 allocation errors and 23 consistency errors in table 'TrustedItem' (object ID 1957582012). DBCC execution completed. If DBCC printed error messages, contact your system administrator. The statement has been terminated.


Can you please suggest the work around for this? I am trying to run dbcc checkdb with REPAIR_ALLOW_DATA_LOSS as suggested by the checkdb command but was just hoping if i can avoid the data loss in production?

Also, can you please suggest how much data loss takes place when we run the checkdb with repair_allow_data_loss command ?

I do not know if we would have a clean backup available since the maintenance plan was not run on this database since long. Is there a way to find out the which is the last clean backup?

Requesting your prompt response.

Thanks

more ▼

asked Nov 14 at 02:50 PM in Default

avatar image

Athy
1

(comments are locked)
10|1200 characters needed characters left

0 answers: sort voted first
Be the first one to answer this question
toggle preview:

Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

SQL Server Central

Need long-form SQL discussion? SQLserverCentral.com is the place.

Topics:

x59
x45
x17
x7

asked: 6 days ago

Seen: 14 times

Last Updated: 6 days ago

Copyright 2017 Redgate Software. Privacy Policy