Hi Friends,
could you please provide the solution for below error,
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -8646911284551352320 (type Unknown), page (289:0). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 62916873 and -1.
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -8646673261154795520 (type Unknown), page ID (3:240120) contains an incorrect page ID in its page header. The PageId in the page header = (0:34871552).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -8596527261321199616 (type Unknown), page ID (3:313995) contains an incorrect page ID in its page header. The PageId in the page header = (16249:36607).
Repairing this error requires other errors to be corrected first.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -8430570274608381952 (type Unknown), page (42240:-1694459136). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29362441 and -1.
Repairing this error requires other errors to be corrected first.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -8234268968676360192 (type Unknown), page (162:4194304). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29362441 and -1.
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -8227198194846531584 (type Unknown), page ID (3:243195) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -7219537657989169152 (type Unknown), page ID (3:958897) contains an incorrect page ID in its page header. The PageId in the page header = (157:10223771).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -6989398602338533376 (type Unknown), page ID (3:1003390) contains an incorrect page ID in its page header. The PageId in the page header = (45824:-1291799808).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -6484976752090152960 (type Unknown), page ID (3:267767) contains an incorrect page ID in its page header. The PageId in the page header = (56064:-771700736).
Repairing this error requires other errors to be corrected first.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -6196736480182796288 (type Unknown), page (51968:-889140736). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 46139657 and -1.
Repairing this error requires other errors to be corrected first.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -6196736480182796288 (type Unknown), page (51968:-889140736). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 62916873 and -1.
Repairing this error requires other errors to be corrected first.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -6196736480182796288 (type Unknown), page (51968:-889140736). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 62916873 and -1.
Repairing this error requires other errors to be corrected first.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -5620272429294157824 (type Unknown), page (51456:-922695424). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 46139657 and -1.
Repairing this error requires other errors to be corrected first.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -5620272429294157824 (type Unknown), page (51456:-922695424). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 62916873 and -1.
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -5476155042144714752 (type Unknown), page ID (3:765605) contains an incorrect page ID in its page header. The PageId in the page header = (52480:-872363264).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -5404096348595159040 (type Unknown), page ID (3:765906) contains an incorrect page ID in its page header. The PageId in the page header = (52224:-872363008).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -5404096348595159040 (type Unknown), page ID (3:765909) contains an incorrect page ID in its page header. The PageId in the page header = (52224:-872363008).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -5404096348595159040 (type Unknown), page ID (3:771290) contains an incorrect page ID in its page header. The PageId in the page header = (52224:-872363008).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -5364349176294146048 (type Unknown), page ID (3:240122) contains an incorrect page ID in its page header. The PageId in the page header = (0:136218).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -5187905974010118144 (type Unknown), page ID (3:292343) contains an incorrect page ID in its page header. The PageId in the page header = (57088:-553591296).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -4827613605706858496 (type Unknown), page ID (3:316919) contains an incorrect page ID in its page header. The PageId in the page header = (58368:-486481408).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -4611474912184696832 (type Unknown), page ID (3:958898) contains an incorrect page ID in its page header. The PageId in the page header = (0:155).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -4611342305308180480 (type Unknown), page ID (3:739323) contains an incorrect page ID in its page header. The PageId in the page header = (0:2560).
Repairing this error requires other errors to be corrected first.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -3963131000715739136 (type Unknown), page (0:67988736). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 62916873 and -1.
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -3674703096400838656 (type Unknown), page ID (3:276982) contains an incorrect page ID in its page header. The PageId in the page header = (55552:-671033344).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -3386469421647134720 (type Unknown), page ID (3:276983) contains an incorrect page ID in its page header. The PageId in the page header = (20302:1265193728).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -3242350934986063872 (type Unknown), page ID (3:495239) contains an incorrect page ID in its page header. The PageId in the page header = (57088:-553591040).
Repairing this error requires other errors to be corrected first.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -3149995260452274176 (type Unknown), page (949:-67108716). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 62916873 and -1.
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -3009811319319691264 (type Unknown), page ID (3:813544) contains an incorrect page ID in its page header. The PageId in the page header = (3072:9699073).
Repairing this error requires other errors to be corrected first.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -2954110663095484416 (type Unknown), page (58624:-452926208). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 62916873 and -1.
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -2882303761517117440 (type Unknown), page ID (3:316918) contains an incorrect page ID in its page header. The PageId in the page header = (146:352390575).
Repairing this error requires other errors to be corrected first.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -2737936781453295616 (type Unknown), page (24430:1392567808). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 62916873 and -1.
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -2710041075769540608 (type Unknown), page ID (3:739322) contains an incorrect page ID in its page header. The PageId in the page header = (7658:2121793808).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -2248816550861340672 (type Unknown), page ID (3:442775) contains an incorrect page ID in its page header. The PageId in the page header = (17638:-536870912).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -2017612633061982208 (type Unknown), page ID (3:486047) contains an incorrect page ID in its page header. The PageId in the page header = (147:-1677669236).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -2013108848751017984 (type Unknown), page ID (3:958899) contains an incorrect page ID in its page header. The PageId in the page header = (155:1898532).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -940533434773143552 (type Unknown), page ID (3:240124) contains an incorrect page ID in its page header. The PageId in the page header = (16256:0).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -543808869014634496 (type Unknown), page ID (3:1000766) contains an incorrect page ID in its page header. The PageId in the page header = (193:12124345).
Repairing this error requires other errors to be corrected first.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -328481156085514240 (type Unknown), page (12:3158062). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 46139657 and -1.
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -308496389791285248 (type Unknown), page ID (3:958901) contains an incorrect page ID in its page header. The PageId in the page header = (155:1898532).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -288211684420747264 (type Unknown), page ID (3:695078) contains an incorrect page ID in its page header. The PageId in the page header = (26842:-550080919).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -288211684420747264 (type Unknown), page ID (3:695079) contains an incorrect page ID in its page header. The PageId in the page header = (26938:-1456050583).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -144115188075855872 (type Unknown), page ID (3:243194) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -128352589379928064 (type Unknown), page ID (3:238582) contains an incorrect page ID in its page header. The PageId in the page header = (50944:115476476).
Repairing this error requires other errors to be corrected first.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page (37803:16560000). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 62916873 and -1.
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (3:89848) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (3:241655) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (3:243192) contains an incorrect page ID in its page header. The PageId in the page header = (0:16256).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (3:243196) contains an incorrect page ID in its page header. The PageId in the page header = (0:16256).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (3:255478) contains an incorrect page ID in its page header. The PageId in the page header = (0:61).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (3:848376) contains an incorrect page ID in its page header. The PageId in the page header = (234:-600309760).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Regards,
Satya.
18.11.13 — 15:58
Есть БП 2.0 на sql 2005, сделал тестирование в sql с помощью dbcc
выдало вот такое сообщение
Msg 2533, Level 16, State 1, Line 2
Table error: page (1:8313949) allocated to object ID 1884077998, index ID 1, partition ID 72057601326841856, alloc unit ID 72057601536032768 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
The repair level on the DBCC statement caused this repair to be bypassed.
Msg 8976, Level 16, State 1, Line 2
Table error: Object ID 1884077998, index ID 1, partition ID 72057601326841856, alloc unit ID 72057601536032768 (type In-row data). Page (1:8313949) was not seen in the scan although its parent (1:8313960) and previous (1:8313948) refer to it. Check any previous errors.
Repairing this error requires other errors to be corrected first.
Msg 8978, Level 16, State 1, Line 2
Table error: Object ID 1884077998, index ID 1, partition ID 72057601326841856, alloc unit ID 72057601536032768 (type In-row data). Page (1:8313950) is missing a reference from previous page (1:8313949). Possible chain linkage problem.
Repairing this error requires other errors to be corrected first.
CHECKDB found 0 allocation errors and 3 consistency errors in table ‘_AccumRg7339’ (object ID 1884077998).
CHECKDB found 0 allocation errors and 3 consistency errors in database ‘account82’.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (account82, repair_rebuild).
если взять архив то можно как то исправить эту проблему, не факт конечно что в архиве таких ошибок нет но все же
если возможно то как действовать?
Изначально проблема проявилась в 1с, при формировании выписок за определенное число (там один не оплаченный документ) и когда его выбираешь и пытаешся заполнить то вылетает база. Сам документ пробовали создать новый но результата не дало.
что вообще выдал sql не пойму, то ли пары записей не хватает, то ли вообще пары таблиц?
1 — 18.11.13 — 16:05
(0) сделай выгрузку — загрузку это самое простое понять есть проблемы с базой или нет
2 — 18.11.13 — 16:09
(1)
итак понятно, что выгрузка не сработает.
(0)
внимательней читайте описание DBCC CHECKDB
3 — 18.11.13 — 16:28
разверните резервные копии протестируйте.
если ошибок нет то в отремонтированную базу перенесите данные из копии либо наоборот из рабочей в копию.
4 — 18.11.13 — 16:30
У меня была такого роде проблема.
Когда админ выдрал питание во время обновления конфы.
Для начала посмотри что в этих таблицах.
Сделай реиндексацию. Ещё есть вариант побороться
утилитой от 1С — chdbfl.
5 — 18.11.13 — 16:40
(0) Ну так там битый регистр накопления.
Можно посмотреть какой: ‘_AccumRg7339’
Может пересчет итогов или перепроведение поможет?
6 — 18.11.13 — 16:44
Пересчет итогов тебе не поможет.
Перепроведение тоже. У тебя в самих таблицах скуля проблемы.
Попробуй тестирование и исправление от 1С. И реиндексацию на SQL.
7 — 18.11.13 — 16:44
(0) Да, еще:
написано: «…repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (account82, repair_rebuild).»
уровень доступа для исправления нужно поменять, тогда dbcc сможет внести исправления, но при этом с большой вероятностью будут потери данных в указанных местах.
http://technet.microsoft.com/ru-ru/library/ms176064.aspx
параметр: REPAIR_ALLOW_DATA_LOSS
8 — 18.11.13 — 16:47
(6) Может и поможет:
«3 consistency errors in table ‘_AccumRg7339′»
нарушена логическая целостность таблицы, как я понимаю:
почистить таблицу и перепровести всё, как вариант!?
9 — 18.11.13 — 16:47
(7) меня тоже это настораживает что данные можно совсем потерять хоть база и будет работать
10 — 18.11.13 — 16:48
(8) перепровести все, это ж сколько будет проводиться?
11 — 18.11.13 — 16:48
Я бы натравил DBCC с нужным доступом, а потом бы почистил тваблицу и перепровел всё. хотя конечно зависит от базы, что там и как-там, какой размер и т.п.
12 — 18.11.13 — 16:48
может можно как то узнать где сбит таблица и как то перетянуть данные из архива?
13 — 18.11.13 — 16:48
(10) всё имеется ввиду, что касается только этого регистра
14 — 18.11.13 — 16:49
(11) база около 100 ГБ
15 — 18.11.13 — 16:49
(12) у тебя похоже только одна таблица сломалась
16 — 18.11.13 — 16:49
(14) мда, это хуже
17 — 18.11.13 — 16:50
(15) вот можно как то только одну таблицу починить, узнать как то на каком этапе поломка и перетащить данные из архива?
18 — 18.11.13 — 16:50
(17)ну разверни бэкап.
проверь, если там все ок, подмени таблицу
Только не забудь все забэкапить.
да и перепроводить все равно прийдется, правда в этом случае можно за недостающий период
19 — 18.11.13 — 16:52
(18) наверное так и придется поступать
20 — 18.11.13 — 17:17
Да пофиг, если это не операция
AccumRg7339 — это регистр накопления, а в БП таком регистре только вспомогательная информация. Для начало узнай что за регистр и дальше по обстоятельству
21 — 18.11.13 — 17:18
вполне возможно что в «сбойной» строке ненужные данные (1с пометила как неактивную запись и не удалила еще за собой)
22 — 18.11.13 — 18:13
(21) из а чего тогда вот это:
Изначально проблема проявилась в 1с, при формировании выписок за определенное число (там один не оплаченный документ) и когда его выбираешь и пытаешься заполнить то вылетает база. Сам документ пробовали создать новый но результата не дало.
23 — 18.11.13 — 19:04
Найди ссылку на этот документ в таблице регистра, вполне возможно, что это все и покажет.
Кста — я так и не увидел, что за регистр.
Вообще, очень похоже на битую таблицу.
24 — 19.11.13 — 07:50
(20) AccumRg7339 — это РегистрНакопления.ИПМПЗОтгруженные, можно как то в таблице sql найти что за документ сделал такие записи, попробовать распровести его или вообще погрохать все записи во всех таблицах от этого документа? Только как найти что это за документ?
Aleksey
25 — 19.11.13 — 10:26
(24) у него же гуид есть
I have a client who uses Microsoft Dynamics NAV with a SQL 2005 database. Two weeks ago they started getting consistency errors. I had
them restore from the last backup, and that seemed to fix the problem.
Yesterday they started getting consistency errors again (in a different area of the database. After everyone was off the system I ran
a DBCC CHECKDB on the database with REPAIR_ALLOW_DATALOSS (the minimum level stated in the first CHECKDB I ran), and it failed (see the log below). They have since restored again, but I have no confidence that this will fix the issue. Can someone help me understand
what is causing the issue and how to fix it?
They have been using this database for years with no problems.
Here is a partial list of the results; the whole list won’t fit in this request:
DBCC results for ‘NAVSQL’.
Service Broker Msg 9675, State 1: Message Types analyzed: 14.
Service Broker Msg 9676, State 1: Service Contracts analyzed: 6.
Service Broker Msg 9667, State 1: Services analyzed: 3.
Service Broker Msg 9668, State 1: Service Queues analyzed: 3.
Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0.
Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0.
Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 281498259750912 (type Unknown), page ID (3:2179484) contains an incorrect page ID in its page header. The PageId in the page header = (8192:65536).
Repairing this error requires other errors to be corrected first.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 3906872676743905280 (type Unknown), page (34749:0). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 46139657 and -4.
The repair level on the DBCC statement caused this repair to be bypassed.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 5641040008258584576 (type Unknown), page ID (4:675855) contains an incorrect page ID in its page header. The PageId in the page header = (256:10150144).
Repairing this error requires other errors to be corrected first.
CHECKDB found 0 allocation errors and 3 consistency errors not associated with any single object.
DBCC results for ‘sys.sysrowsetcolumns’.
There are 32308 rows in 186 pages for object «sys.sysrowsetcolumns».
…
CHECKDB found 0 allocation errors and 44 consistency errors in database ‘NAVSQL’.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Bob Brown
I’ve included the log. Any ideas on how to fix these errors?
==============================================
Server: Msg 1505, Level 16, State 1, Line 1
CREATE UNIQUE INDEX terminated because a duplicate key was found for index ID 1. Most significant primary key is ‘Database Administrators’.
Server: Msg 1505, Level 16, State 1, Line 1
CREATE UNIQUE INDEX terminated because a duplicate key was found for index ID 1. Most significant primary key is ‘type 24, len 16’.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 0, index ID 0: Page (1:166140) could not be processed. See other errors for details.
DBCC results for ‘MOMReporting’.
Repairing this error requires other errors to be corrected first.
CHECKDB found 1 allocation errors and 0 consistency errors not associated with any single object.
DBCC results for ‘sysobjects’.
There are 874 rows in 17 pages for object ‘sysobjects’.
DBCC results for ‘sysindexes’.
There are 241 rows in 12 pages for object ‘sysindexes’.
DBCC results for ‘syscolumns’.
There are 3211 rows in 48 pages for object ‘syscolumns’.
DBCC results for ‘systypes’.
There are 26 rows in 1 pages for object ‘systypes’.
DBCC results for ‘syscomments’.
There are 843 rows in 136 pages for object ‘syscomments’.
DBCC results for ‘sysfiles1’.
There are 2 rows in 1 pages for object ‘sysfiles1’.
DBCC results for ‘syspermissions’.
There are 58 rows in 1 pages for object ‘syspermissions’.
DBCC results for ‘sysusers’.
There are 22 rows in 1 pages for object ‘sysusers’.
DBCC results for ‘sysproperties’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:589) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:2424) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:2425) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:2426) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:2427) in database ID 8 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’.
There are 0 rows in 0 pages for object ‘sysproperties’.
DBCC results for ‘sysdepends’.
There are 5079 rows in 26 pages for object ‘sysdepends’.
DBCC results for ‘sysreferences’.
There are 0 rows in 1 pages for object ‘sysreferences’.
DBCC results for ‘sysfulltextcatalogs’.
There are 0 rows in 0 pages for object ‘sysfulltextcatalogs’.
DBCC results for ‘sysfulltextnotify’.
There are 0 rows in 0 pages for object ‘sysfulltextnotify’.
DBCC results for ‘sysfilegroups’.
There are 1 rows in 1 pages for object ‘sysfilegroups’.
DBCC results for ‘ProcessRule’.
Could not repair this error.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:2428) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:2429) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:3683) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:3684) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:3685) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:3686) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:3687) in database ID 8 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’.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:3720) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:4564) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:3728) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:3729) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:3731) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:3732) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:3733) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:3734) in database ID 8 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’.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:4565) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:3747) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:3751) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:3768) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:3769) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:4566) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:4567) in database ID 8 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’.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6884) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:3773) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:4233) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:4247) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:4282) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:4553) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:4554) in database ID 8 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’.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6886) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:4557) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:4558) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:4559) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:4562) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:4563) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6952) in database ID 8 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’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6953) in database ID 8 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’.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
There are 5893 rows in 259 pages for object ‘ProcessRule’.
CHECKDB found 42 allocation errors and 0 consistency errors in table ‘ProcessRule’ (object ID 2099048).
DBCC results for ‘AlertEventSuppression’.
There are 13180 rows in 326 pages for object ‘AlertEventSuppression’.
DBCC results for ‘AlertHistory’.
There are 27921 rows in 2954 pages for object ‘AlertHistory’.
DBCC results for ‘AlertLevel’.
There are 7 rows in 1 pages for object ‘AlertLevel’.
DBCC results for ‘ProcessRuleComment’.
There are 10365 rows in 6088 pages for object ‘ProcessRuleComment’.
DBCC results for ‘AlertToEvent’.
There are 1889 rows in 18 pages for object ‘AlertToEvent’.
DBCC results for ‘ProcessRuleMembership’.
There are 5896 rows in 49 pages for object ‘ProcessRuleMembership’.
DBCC results for ‘Component’.
There are 64 rows in 1 pages for object ‘Component’.
DBCC results for ‘ProcessRuleToNotifyGroup’.
There are 235 rows in 2 pages for object ‘ProcessRuleToNotifyGroup’.
DBCC results for ‘Computer’.
There are 850 rows in 25 pages for object ‘Computer’.
DBCC results for ‘ProcessRuleToScript’.
There are 309 rows in 3 pages for object ‘ProcessRuleToScript’.
DBCC results for ‘ProviderInstance’.
There are 0 rows in 1 pages for object ‘ProviderInstance’.
DBCC results for ‘ProviderType’.
There are 7 rows in 1 pages for object ‘ProviderType’.
DBCC results for ‘ComputerAttribute’.
There are 3479 rows in 57 pages for object ‘ComputerAttribute’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:70210) in database ID 8 is allocated in the SGAM (1:3) and PFS (1:64704), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:166137) in database ID 8 is allocated in the SGAM (1:3) and PFS (1:161760), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
DBCC results for ‘ResolutionState’.
There are 7 rows in 1 pages for object ‘ResolutionState’.
DBCC results for ‘ComputerAttributeDefinition’.
There are 0 rows in 1 pages for object ‘ComputerAttributeDefinition’.
DBCC results for ‘RuleType’.
There are 14 rows in 1 pages for object ‘RuleType’.
DBCC results for ‘ComputerResponsibility’.
There are 114 rows in 3 pages for object ‘ComputerResponsibility’.
DBCC results for ‘RuleTypeToProviderType’.
There are 36 rows in 1 pages for object ‘RuleTypeToProviderType’.
DBCC results for ‘ComputerRule’.
There are 70 rows in 6 pages for object ‘ComputerRule’.
DBCC results for ‘SampledNumericData’.
There are 189128131 rows in 1518227 pages for object ‘SampledNumericData’.
DBCC results for ‘SampledNumericDataSource’.
Repairing this error requires other errors to be corrected first.
There are 6663 rows in 72 pages for object ‘SampledNumericDataSource’.
CHECKDB found 1 allocation errors and 0 consistency errors in table ‘SampledNumericDataSource’ (object ID 658101385).
DBCC results for ‘Script’.
Repairing this error requires other errors to be corrected first.
There are 54 rows in 3 pages for object ‘Script’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:166196) in database ID 8 is allocated in the SGAM (1:3) and PFS (1:161760), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:166199) in database ID 8 is allocated in the SGAM (1:3) and PFS (1:161760), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:166221) in database ID 8 is allocated in the SGAM (1:3) and PFS (1:161760), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
CHECKDB found 1 allocation errors and 0 consistency errors in table ‘Script’ (object ID 706101556).
DBCC results for ‘ComputerRuleToProcessRuleGroup’.
There are 110 rows in 1 pages for object ‘ComputerRuleToProcessRuleGroup’.
DBCC results for ‘StringLocalization’.
There are 0 rows in 0 pages for object ‘StringLocalization’.
DBCC results for ‘ComputerToComputerRule’.
There are 2455 rows in 20 pages for object ‘ComputerToComputerRule’.
DBCC results for ‘Task’.
There are 0 rows in 0 pages for object ‘Task’.
DBCC results for ‘Configuration’.
There are 50 rows in 2 pages for object ‘Configuration’.
DBCC results for ‘TodayStatistics’.
There are 1 rows in 1 pages for object ‘TodayStatistics’.
DBCC results for ‘MOMReplicationTimeStamp’.
There are 1 rows in 1 pages for object ‘MOMReplicationTimeStamp’.
DBCC results for ‘User’.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:166222) in database ID 8 is allocated in the SGAM (1:3) and PFS (1:161760), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:166304) in database ID 8 is allocated in the SGAM (1:3) and PFS (1:161760), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:166306) in database ID 8 is allocated in the SGAM (1:3) and PFS (1:161760), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:166307) in database ID 8 is allocated in the SGAM (1:3) and PFS (1:161760), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:166140) in database ID 8 is allocated in the SGAM (1:3) and PFS (1:161760), but was not allocated in any IAM. PFS flags ‘IAM_PG MIXED_EXT ALLOCATED 0_PCT_FULL’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:166216) in database ID 8 is allocated in the SGAM (1:3) and PFS (1:161760), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:166218) in database ID 8 is allocated in the SGAM (1:3) and PFS (1:161760), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:166220) in database ID 8 is allocated in the SGAM (1:3) and PFS (1:161760), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:166223) in database ID 8 is allocated in the SGAM (1:3) and PFS (1:161760), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:166308) in database ID 8 is allocated in the SGAM (1:3) and PFS (1:161760), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:166309) in database ID 8 is allocated in the SGAM (1:3) and PFS (1:161760), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:166310) in database ID 8 is allocated in the SGAM (1:3) and PFS (1:161760), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
There are 129854 rows in 1335 pages for object ‘User’.
CHECKDB found 15 allocation errors and 0 consistency errors in table ‘User’ (object ID 866102126).
DBCC results for ‘dtproperties’.
There are 0 rows in 0 pages for object ‘dtproperties’.
DBCC results for ‘DasServers’.
There are 1 rows in 1 pages for object ‘DasServers’.
DBCC results for ‘UserDefinedField’.
There are 5 rows in 1 pages for object ‘UserDefinedField’.
DBCC results for ‘Event’.
There are 4587340 rows in 760613 pages for object ‘Event’.
DBCC results for ‘Vendor’.
There are 0 rows in 0 pages for object ‘Vendor’.
DBCC results for ‘EventConsolidated’.
There are 9809 rows in 200 pages for object ‘EventConsolidated’.
DBCC results for ‘AuditLog’.
There are 0 rows in 0 pages for object ‘AuditLog’.
DBCC results for ‘EventParam’.
There are 73809536 rows in 1087576 pages for object ‘EventParam’.
DBCC results for ‘AuditLogValues’.
There are 0 rows in 0 pages for object ‘AuditLogValues’.
DBCC results for ‘EventParamName’.
There are 14 rows in 1 pages for object ‘EventParamName’.
DBCC results for ‘GroomLock’.
There are 2 rows in 1 pages for object ‘GroomLock’.
DBCC results for ‘EventSource’.
There are 1108 rows in 22 pages for object ‘EventSource’.
DBCC results for ‘EventType’.
There are 6 rows in 1 pages for object ‘EventType’.
DBCC results for ‘GroomAttribute’.
There are 5 rows in 1 pages for object ‘GroomAttribute’.
DBCC results for ‘GroomHistory’.
There are 4371159 rows in 35021 pages for object ‘GroomHistory’.
DBCC results for ‘GroomJob’.
There are 9 rows in 1 pages for object ‘GroomJob’.
DBCC results for ‘GroomJobCriteria’.
There are 17 rows in 1 pages for object ‘GroomJobCriteria’.
DBCC results for ‘GuiClass’.
There are 0 rows in 0 pages for object ‘GuiClass’.
DBCC results for ‘KBase’.
There are 0 rows in 0 pages for object ‘KBase’.
DBCC results for ‘KBaseComment’.
There are 0 rows in 0 pages for object ‘KBaseComment’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:5741163) in database ID 8 is allocated in the SGAM (1:5623553) and PFS (1:5734392), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:5741168) in database ID 8 is allocated in the SGAM (1:5623553) and PFS (1:5734392), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:5741172) in database ID 8 is allocated in the SGAM (1:5623553) and PFS (1:5734392), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:5741173) in database ID 8 is allocated in the SGAM (1:5623553) and PFS (1:5734392), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:5741174) in database ID 8 is allocated in the SGAM (1:5623553) and PFS (1:5734392), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
DBCC results for ‘KBaseHistory’.
There are 0 rows in 0 pages for object ‘KBaseHistory’.
DBCC results for ‘KBaseSection’.
Repairing this error requires other errors to be corrected first.
There are 11 rows in 1 pages for object ‘KBaseSection’.
CHECKDB found 1 allocation errors and 0 consistency errors in table ‘KBaseSection’ (object ID 1589580701).
DBCC results for ‘KpcType’.
Repairing this error requires other errors to be corrected first.
There are 4 rows in 1 pages for object ‘KpcType’.
CHECKDB found 1 allocation errors and 0 consistency errors in table ‘KpcType’ (object ID 1637580872).
DBCC results for ‘License’.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6170266) in database ID 8 is allocated in the SGAM (1:6134785) and PFS (1:6163056), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6170270) in database ID 8 is allocated in the SGAM (1:6134785) and PFS (1:6163056), but was not allocated in any IAM. PFS flags ‘MIXED_EXT ALLOCATED 0_PCT_FULL’.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 1797581442, index ID 1. Page (1:124) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 1845581613, index ID 1. Page (1:175) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.
Repairing this error requires other errors to be corrected first.
Repairing this error requires other errors to be corrected first.
There are 11 rows in 5 pages for object ‘License’.
CHECKDB found 4 allocation errors and 0 consistency errors in table ‘License’ (object ID 1685581043).
DBCC results for ‘MessageDll’.
Repairing this error requires other errors to be corrected first.
There are 96 rows in 1 pages for object ‘MessageDll’.
CHECKDB found 1 allocation errors and 0 consistency errors in table ‘MessageDll’ (object ID 1701581100).
DBCC results for ‘MonitorView’.
There are 0 rows in 1 pages for object ‘MonitorView’.
DBCC results for ‘NotifyGroup’.
Could not repair this error.
There are 24 rows in 2 pages for object ‘NotifyGroup’.
CHECKDB found 0 allocation errors and 1 consistency errors in table ‘NotifyGroup’ (object ID 1797581442).
DBCC results for ‘NotifyGroupMember’.
Could not repair this error.
There are 14 rows in 2 pages for object ‘NotifyGroupMember’.
CHECKDB found 0 allocation errors and 1 consistency errors in table ‘NotifyGroupMember’ (object ID 1845581613).
DBCC results for ‘NotifyHistory’.
There are 0 rows in 0 pages for object ‘NotifyHistory’.
DBCC results for ‘Operator’.
There are 0 rows in 1 pages for object ‘Operator’.
DBCC results for ‘DasLog’.
There are 11532 rows in 328 pages for object ‘DasLog’.
DBCC results for ‘Akm’.
There are 0 rows in 0 pages for object ‘Akm’.
DBCC results for ‘PerfmonCounterScale’.
There are 214 rows in 4 pages for object ‘PerfmonCounterScale’.
DBCC results for ‘AkmToMonitorView’.
There are 0 rows in 0 pages for object ‘AkmToMonitorView’.
DBCC results for ‘Alert’.
There are 15168 rows in 3844 pages for object ‘Alert’.
CHECKDB found 67 allocation errors and 2 consistency errors in database ‘MOMReporting’.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (MOMReporting repair_allow_data_loss).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
The statement has been terminated.
========================================================================
Any help is greatly appreciated. Thanks!
Being day one of DBBC Command month at SteveStedman.com, today’s featured DBCC Command is DBCC CHECKALLOC.
Description:
DBCC CheckAlloc checks and can repair disk space allocation structures for a database. DBCC CheckAlloc checks the allocation for all pages in the database compared to their internal structures representing those pages. When you run DBCC CheckDB it internally runs the equivalent of DBCC CheckAlloc as part of the process.
DBCC CHECKALLOC Syntax:
dbcc checkalloc
(
[ { 'database_name' | database_id | 0 } ]
[ , NOINDEX |
{ REPAIR_ALLOW_DATA_LOSS
| REPAIR_FAST
| REPAIR_REBUILD
} ]
)
[ WITH
{
[ ALL_ERRORMSGS ]
[ , [ NO_INFOMSGS ] ]
[ , [ TABLOCK ] ]
[ , [ ESTIMATEONLY ] ]
}
]
DBCC CheckAlloc Example:
Running DBCC CheckAlloc without a parameter checks the current database. Alternatively the first parameter can specify a database name or database id.
-- Check the current database. DBCC CHECKALLOC;
Which gives the following output:
DBCC results for 'cte_demo'.
***************************************************************
Table sys.sysrscols Object ID 3.
Index ID 1, partition ID 196608, alloc unit ID 196608 (type In-row data). FirstIAM (1:157). Root (1:158). Dpages 12.
Index ID 1, partition ID 196608, alloc unit ID 196608 (type In-row data). 14 pages used in 1 dedicated extents.
Total number of extents is 1.
***************************************************************
Table sys.sysrowsets Object ID 5.
Index ID 1, partition ID 327680, alloc unit ID 327680 (type In-row data). FirstIAM (1:131). Root (1:17). Dpages 1.
Index ID 1, partition ID 327680, alloc unit ID 327680 (type In-row data). 2 pages used in 0 dedicated extents.
Total number of extents is 0.
***************************************************************
Table sys.sysclones Object ID 6.
Index ID 1, partition ID 281474977103872, alloc unit ID 281474977103872 (type In-row data). FirstIAM (0:0). Root (0:0). Dpages 0.
Index ID 1, partition ID 281474977103872, alloc unit ID 281474977103872 (type In-row data). 0 pages used in 0 dedicated extents.
Total number of extents is 0.
***************************************************************
Table sys.sysallocunits Object ID 7.
Index ID 1, partition ID 458752, alloc unit ID 458752 (type In-row data). FirstIAM (1:21). Root (1:139). Dpages 0.
Index ID 1, partition ID 458752, alloc unit ID 458752 (type In-row data). 4 pages used in 0 dedicated extents.
Index ID 2, partition ID 562949953880064, alloc unit ID 562949953880064 (type In-row data). FirstIAM (1:18). Root (1:16). Dpages 1.
Index ID 2, partition ID 562949953880064, alloc unit ID 562949953880064 (type In-row data). 2 pages used in 0 dedicated extents.
Total number of extents is 0.
***************************************************************
.
.
.
Dozens of rows removed
.
.
.
***************************************************************
Table sys.filetable_updates_2105058535 Object ID 2105058535.
Index ID 1, partition ID 72057594038976512, alloc unit ID 72057594043301888 (type In-row data). FirstIAM (0:0). Root (0:0). Dpages 0.
Index ID 1, partition ID 72057594038976512, alloc unit ID 72057594043301888 (type In-row data). 0 pages used in 0 dedicated extents.
Total number of extents is 0.
File 1. The number of extents = 35, used pages = 242, and reserved pages = 274.
File 1 (number of mixed extents = 21, mixed pages = 162).
Object ID 3, index ID 1, partition ID 196608, alloc unit ID 196608 (type In-row data), data extents 1, pages 14, mixed extent pages 9.
Object ID 5, index ID 1, partition ID 327680, alloc unit ID 327680 (type In-row data), data extents 0, pages 2, mixed extent pages 2.
Object ID 7, index ID 1, partition ID 458752, alloc unit ID 458752 (type In-row data), data extents 0, pages 4, mixed extent pages 4.
Object ID 7, index ID 2, partition ID 562949953880064, alloc unit ID 562949953880064 (type In-row data), index extents 0, pages 2, mixed extent pages 2.
Object ID 8, index ID 0, partition ID 524288, alloc unit ID 524288 (type In-row data), data extents 0, pages 2, mixed extent pages 2.
Object ID 20, index ID 1, partition ID 281474978021376, alloc unit ID 281474978021376 (type In-row data), data extents 0, pages 2, mixed extent pages 2.
Object ID 23, index ID 1, partition ID 281474978217984, alloc unit ID 281474978217984 (type In-row data), data extents 0, pages 2, mixed extent pages 2.
Object ID 24, index ID 1, partition ID 281474978283520, alloc unit ID 281474978283520 (type In-row data), data extents 0, pages 2, mixed extent pages 2.
Object ID 27, index ID 1, partition ID 281474978480128, alloc unit ID 281474978480128 (type In-row data), data extents 0, pages 2, mixed extent pages 2.
Object ID 27, index ID 2, partition ID 562949955190784, alloc unit ID 562949955190784 (type In-row data), index extents 0, pages 2, mixed extent pages 2.
Object ID 27, index ID 3, partition ID 844424931901440, alloc unit ID 844424931901440 (type In-row data), index extents 0, pages 2, mixed extent pages 2.
Object ID 29, index ID 1, partition ID 281474978611200, alloc unit ID 281474978611200 (type In-row data), data extents 0, pages 2, mixed extent pages 2.
Object ID 34, index ID 1, partition ID 281474978938880, alloc unit ID 281474978938880 (type In-row data), data extents 3, pages 31, mixed extent pages 9.
Object ID 34, index ID 2, partition ID 562949955649536, alloc unit ID 562949955649536 (type In-row data), index extents 3, pages 26, mixed extent pages 9.
Object ID 34, index ID 3, partition ID 844424932360192, alloc unit ID 844424932360192 (type In-row data), index extents 3, pages 26, mixed extent pages 9.
Object ID 34, index ID 4, partition ID 1125899909070848, alloc unit ID 1125899909070848 (type In-row data), index extents 0, pages 7, mixed extent pages 7.
Object ID 41, index ID 1, partition ID 281474979397632, alloc unit ID 281474979397632 (type In-row data), data extents 1, pages 13, mixed extent pages 9.
Object ID 41, index ID 2, partition ID 562949956108288, alloc unit ID 562949956108288 (type In-row data), index extents 0, pages 7, mixed extent pages 7.
Object ID 44, index ID 1, partition ID 281474979594240, alloc unit ID 281474979594240 (type In-row data), data extents 0, pages 2, mixed extent pages 2.
Object ID 44, index ID 2, partition ID 562949956304896, alloc unit ID 562949956304896 (type In-row data), index extents 0, pages 2, mixed extent pages 2.
Object ID 50, index ID 1, partition ID 281474979987456, alloc unit ID 281474979987456 (type In-row data), data extents 0, pages 2, mixed extent pages 2.
Object ID 50, index ID 2, partition ID 562949956698112, alloc unit ID 562949956698112 (type In-row data), index extents 0, pages 2, mixed extent pages 2.
Object ID 50, index ID 3, partition ID 844424933408768, alloc unit ID 844424933408768 (type In-row data), index extents 0, pages 2, mixed extent pages 2.
Object ID 54, index ID 1, partition ID 281474980249600, alloc unit ID 281474980249600 (type In-row data), data extents 0, pages 4, mixed extent pages 4.
Object ID 54, index ID 2, partition ID 562949956960256, alloc unit ID 562949956960256 (type In-row data), index extents 0, pages 2, mixed extent pages 2.
Object ID 55, index ID 1, partition ID 281474980315136, alloc unit ID 281474980315136 (type In-row data), data extents 0, pages 4, mixed extent pages 4.
Object ID 55, index ID 2, partition ID 562949957025792, alloc unit ID 562949957025792 (type In-row data), index extents 0, pages 2, mixed extent pages 2.
Object ID 58, index ID 1, partition ID 281474980511744, alloc unit ID 72057594037993472 (type In-row data), data extents 0, pages 2, mixed extent pages 2.
Object ID 58, index ID 2, partition ID 562949957222400, alloc unit ID 72057594038059008 (type In-row data), index extents 0, pages 2, mixed extent pages 2.
Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data), index extents 0, pages 5, mixed extent pages 5.
Object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 281474980642816 (type In-row data), data extents 2, pages 18, mixed extent pages 9.
Object ID 64, index ID 1, partition ID 281474980904960, alloc unit ID 281474980904960 (type In-row data), data extents 0, pages 2, mixed extent pages 2.
Object ID 64, index ID 2, partition ID 562949957615616, alloc unit ID 562949957615616 (type In-row data), index extents 0, pages 2, mixed extent pages 2.
Object ID 69, index ID 1, partition ID 281474981232640, alloc unit ID 72057594039697408 (type In-row data), data extents 0, pages 2, mixed extent pages 2.
Object ID 69, index ID 2, partition ID 562949957943296, alloc unit ID 72057594039762944 (type In-row data), index extents 0, pages 2, mixed extent pages 2.
Object ID 69, index ID 3, partition ID 844424934653952, alloc unit ID 72057594039828480 (type In-row data), index extents 0, pages 2, mixed extent pages 2.
Object ID 74, index ID 1, partition ID 281474981560320, alloc unit ID 281474981560320 (type In-row data), data extents 0, pages 2, mixed extent pages 2.
Object ID 74, index ID 2, partition ID 562949958270976, alloc unit ID 562949958270976 (type In-row data), index extents 0, pages 2, mixed extent pages 2.
Object ID 75, index ID 1, partition ID 281474981625856, alloc unit ID 281474981625856 (type In-row data), data extents 0, pages 2, mixed extent pages 2.
Object ID 75, index ID 2, partition ID 562949958336512, alloc unit ID 562949958336512 (type In-row data), index extents 0, pages 2, mixed extent pages 2.
Object ID 90, index ID 1, partition ID 281474982608896, alloc unit ID 72057594038583296 (type In-row data), data extents 0, pages 2, mixed extent pages 2.
Object ID 90, index ID 2, partition ID 562949959319552, alloc unit ID 72057594038648832 (type In-row data), index extents 0, pages 2, mixed extent pages 2.
Object ID 91, index ID 1, partition ID 281474982674432, alloc unit ID 72057594038779904 (type In-row data), data extents 0, pages 2, mixed extent pages 2.
Object ID 91, index ID 2, partition ID 562949959385088, alloc unit ID 72057594038845440 (type In-row data), index extents 0, pages 2, mixed extent pages 2.
Object ID 92, index ID 1, partition ID 281474982739968, alloc unit ID 72057594038976512 (type In-row data), data extents 0, pages 2, mixed extent pages 2.
Object ID 93, index ID 1, partition ID 281474982805504, alloc unit ID 72057594039107584 (type In-row data), data extents 0, pages 2, mixed extent pages 2.
Object ID 93, index ID 2, partition ID 562949959516160, alloc unit ID 72057594039173120 (type In-row data), index extents 0, pages 2, mixed extent pages 2.
Object ID 97, index ID 1, partition ID 281474983067648, alloc unit ID 72057594038190080 (type In-row data), data extents 0, pages 2, mixed extent pages 2.
Object ID 97, index ID 2, partition ID 562949959778304, alloc unit ID 72057594038255616 (type In-row data), index extents 0, pages 2, mixed extent pages 2.
Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type Unknown), index extents 1, pages 7, mixed extent pages 1.
Object ID 245575913, index ID 0, partition ID 72057594039042048, alloc unit ID 72057594043432960 (type In-row data), data extents 0, pages 2, mixed extent pages 2.
The total number of extents = 35, used pages = 242, and reserved pages = 274 in this database.
(number of mixed extents = 21, mixed pages = 162) in this database.
CHECKALLOC found 0 allocation errors and 0 consistency errors in database 'cte_demo'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
If errors were encountered on the output, it states to contact your system administrator. But what if you are the system administrator or DBA… At that point your safest option is to restore from backup. The unsafe alternative is to run DBCC CheckAlloc with one of the repair options to attempt to fix your database corruption.
DBCC CheckAlloc Example with Corruption:
Here we will be using the dbcc_corruption database with a table named Departments. The IAM on the Departments table is corrupt, so DBCC_CheckAlloc produces the following errors:
USE [dbcc_corruption]; DBCC CheckAlloc();
DBCC results for ‘dbcc_corruption’.
Msg 8939, Level 16, State 98, Line 2
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 99360666784432128 (type
Unknown), page (1:272). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -6.
Msg 8928, Level 16, State 6, Line 2
Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown): Page (1:272) could
not be processed. See other errors for details.
Msg 8906, Level 16, State 1, Line 2
Page (1:272) in database ID 17 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’.
CHECKALLOC found 3 allocation errors and 0 consistency errors not associated with any
single object.
***************************************************************
Table sys.sysrscols Object ID 3.
Index ID 1, partition ID 196608, alloc unit ID 196608 (type In-row data). FirstIAM (1:157).
Root (1:158). Dpages 12.
Index ID 1, partition ID 196608, alloc unit ID 196608 (type In-row data). 14 pages used in 1
dedicated extents.
Total number of extents is 1.
***************************************************************
Now to go about fixing it. First I would recommend checking the contents of the table to see if it look correct, if the table contents don’t look right it may require to restore from backup:
SELECT * FROM Departments;
We see 4 rows which tells us that our table data is ok. It might be a good idea at this point to copy the data from this table into another table. For now we will attempt to repair the table, so we run the DBCC CheckAlloc with REPAIR_REBUILD option. Keep in mind that DBCC CheckAlloc must be run in single user mode.
ALTER DATABASE [dbcc_corruption] SET SINGLE_USER WITH ROLLBACK IMMEDIATE; DBCC CheckAlloc(dbcc_corruption, REPAIR_REBUILD); ALTER DATABASE [dbcc_corruption] SET MULTI_USER WITH ROLLBACK IMMEDIATE;
DBCC results for ‘dbcc_corruption’.
Msg 8928, Level 16, State 6, Line 2
Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown): Page (1:272) could
not be processed. See other errors for details.
Repairing this error requires other errors to be corrected first.
Msg 8906, Level 16, State 1, Line 2
Page (1:272) in database ID 17 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’.
The repair level on the DBCC statement caused this repair to be bypassed.
Msg 8939, Level 16, State 98, Line 2
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 99360666784432128 (type
Unknown), page (1:272). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -6.
Repairing this error requires other errors to be corrected first.
CHECKALLOC found 3 allocation errors and 0 consistency errors not associated with any
single object.
***************************************************************
Indicating failure, the REPAIR_REBUILD option for DBCC CheckAlloc won’t do the job. Now for the REPAIR_ALLOW_DATA_LOSS option. You should have copied the contents of this table into another table before trying this.
ALTER DATABASE [dbcc_corruption] SET SINGLE_USER WITH ROLLBACK IMMEDIATE; DBCC CheckAlloc(dbcc_corruption, REPAIR_ALLOW_DATA_LOSS); ALTER DATABASE [dbcc_corruption] SET MULTI_USER WITH ROLLBACK IMMEDIATE;
DBCC results for ‘dbcc_corruption’.
Repair: The page (1:272) has been deallocated from object ID 0, index ID -1,
partition ID 0, alloc unit ID 99360666784432128 (type Unknown).
Msg 8928, Level 16, State 6, Line 2
Object ID 0, index ID -1, partition ID 0, alloc
unit ID 0 (type Unknown): Page (1:272) could not be processed. See other
errors for details.
The error has been repaired.
Msg 8906, Level 16, State 1, Line 2
Page (1:272) in database ID 17 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’.
The error has been repaired.
Msg 8939, Level 16, State 98, Line 2
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 99360666784432128
(type Unknown), page (1:272). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -6.
The error has been repaired.
CHECKALLOC found 3 allocation errors and 0 consistency errors not associated with any
single object.
CHECKALLOC fixed 3 allocation errors and 0 consistency errors not associated with any
single object.
***************************************************************
This time the error is repaired with DBCC CheckAlloc. But now for the real test, does our table data look alright?
SELECT * FROM Departments;
Which looks good. Now to run DBCC CheckAlloc to see how things look.
USE [dbcc_corruption]; DBCC CheckAlloc();
…. output truncated
The total number of extents = 35, used pages = 244, and reserved pages =
275 in this database. (number of mixed extents = 21, mixed pages = 163)
in this database.
CHECKALLOC found 0 allocation errors and 0 consistency errors in database
‘dbcc_corruption’.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
Here we see that the fix worked, and the table is fine. The next step after DBCC CheckAlloc would be to run DBCC CheckDB to see if the rest of the database is fine also. In this case the rest of the database is fine.
DBCC CheckAlloc Notes:
DBCC CheckAlloc along with DBCC CheckTable for every object in the database are called when DBCC CheckDB is run. Running DBCC CheckAlloc or DBCC CheckTable would be redundant after running DBCC CheckDB.
For more information see TSQL Wiki DBCC checkalloc.
DBCC Command month at SteveStedman.com is almost as much fun as shark week.
Steve and the team at Stedman Solutions are here for all your SQL Server needs.
Contact us today for your free 30 minute consultation..
We are ready to help!
To get it out of the way, in this scenario we are repairing a number database where no backups were taken from before the corruption, so restoring a backup is not an option. Not my database 
Upon running DBCC CHECKDB with REPAIR_ALLOW_DATA_LOSS we get thousands of errors that look like this:
Msg 8928, Level 16, State 1, Line 7
Object ID 2105058535, index ID 1, partition ID 72057594038779904, alloc unit ID 72057594039762944 (type LOB data): Page (1:24911) could not be processed. See other errors for details.
Repairing this error requires other errors to be corrected first.
Msg 8965, Level 16, State 1, Line 7
Table error: Object ID 2105058535, index ID 1, partition ID 72057594038779904, alloc unit ID 72057594039762944 (type LOB data). The off-row data node at page (1:24911), slot 0, text ID 265289728 is referenced by page (1:24820), slot 0, but was not seen in the scan.
Repairing this error requires other errors to be corrected first.
Msg 8928, Level 16, State 1, Line 7
Object ID 2105058535, index ID 1, partition ID 72057594038779904, alloc unit ID 72057594039762944 (type LOB data): Page (1:24912) could not be processed. See other errors for details.
Repairing this error requires other errors to be corrected first.
Msg 8965, Level 16, State 1, Line 7
Table error: Object ID 2105058535, index ID 1, partition ID 72057594038779904, alloc unit ID 72057594039762944 (type LOB data). The off-row data node at page (1:24912), slot 0, text ID 265289728 is referenced by page (1:24820), slot 0, but was not seen in the scan.
Repairing this error requires other errors to be corrected first.
Msg 8928, Level 16, State 1, Line 7
Object ID 2105058535, index ID 1, partition ID 72057594038779904, alloc unit ID 72057594039762944 (type LOB data): Page (1:24913) could not be processed. See other errors for details.
Repairing this error requires other errors to be corrected first.
Running it repeatedly does not reduce the errors, so it looks like DBCC cannot repair this.
My next thought was to try and identify and delete the problematic rows in the table. When I tried deleting a known-problematic row though, it also errored, so my current thought is to extract known-good rows into a new table with the same schema as the old, drop the old table and rename the new one to match the old one.
The problem with this is that SQL Server, instead of providing a catchable error, simply drops the connection whenever a problem row is encountered, so I can’t seem to find a programmatic way to identify the ‘good’ rows.
Is there any way in T-SQL to force it to provide a nice catchable error so I can iterate through the table and pull out the good rows, or some ‘advanced’ mode of DBCC CHECKDB that might be able to repair it that isn’t obvious anywhere on the web?
use db_tank dbcc checkdb
- An error is as follows
It can be known from index ID 3 that is a problem with non-aggregation index.
Msg 8978, Level 16, State 1, Line 3 Table error: Object ID 477960779, index ID 3, partition ID 72057594074890240, alloc unit ID 72057594081509376 (type In-row data). Page (1:2335514) is missing a reference from previous page (1:3628311). Possible chain linkage problem. Msg 8978, Level 16, State 1, Line 3 Table error: Object ID 477960779, index ID 3, partition ID 72057594074890240, alloc unit ID 72057594081509376 (type In-row data). Page (1:2839352) is missing a reference from previous page (1:3598023). Possible chain linkage problem. Msg 8928, Level 16, State 1, Line 3 Object ID 477960779, index ID 3, partition ID 72057594074890240, alloc unit ID 72057594081509376 (type In-row data): Page (1:3598023) could not be processed. See other errors for details. Msg 8939, Level 16, State 98, Line 3 Table error: Object ID 477960779, index ID 3, partition ID 72057594074890240, alloc unit ID 72057594081509376 (type In-row data), page (1:3598023). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 46270473 and -4. Msg 8976, Level 16, State 1, Line 3 Table error: Object ID 477960779, index ID 3, partition ID 72057594074890240, alloc unit ID 72057594081509376 (type In-row data). Page (1:3598023) was not seen in the scan although its parent (1:7723523) and previous (1:7723545) refer to it. Check any previous errors. Msg 8928, Level 16, State 1, Line 3 Object ID 477960779, index ID 3, partition ID 72057594074890240, alloc unit ID 72057594081509376 (type In-row data): Page (1:3628311) could not be processed. See other errors for details. Msg 8939, Level 16, State 98, Line 3 Table error: Object ID 477960779, index ID 3, partition ID 72057594074890240, alloc unit ID 72057594081509376 (type In-row data), page (1:3628311). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 348260361 and -4. Msg 8976, Level 16, State 1, Line 3 Table error: Object ID 477960779, index ID 3, partition ID 72057594074890240, alloc unit ID 72057594081509376 (type In-row data). Page (1:3628311) was not seen in the scan although its parent (1:13500023) and previous (1:3075648) refer to it. Check any previous errors.
1, initial attempt — non-destructive data repair
— Switch single user mode
alter database db_tank
set single_user with rollback IMMEDIATE
dbcc checkdb('db_tank', repair_rebuild) - Try non-destructive repair
- The result is as follows
DBCC results for 'Sys_Users_Goods'. Msg 8978, Level 16, State 1, Line 1 Table error: Object ID 477960779, index ID 3, partition ID 72057594074890240, alloc unit ID 72057594081509376 (type In-row data). Page (1:2335514) is missing a reference from previous page (1:3628311). Possible chain linkage problem. Repairing this error requires other errors to be corrected first. Msg 8978, Level 16, State 1, Line 1 Table error: Object ID 477960779, index ID 3, partition ID 72057594074890240, alloc unit ID 72057594081509376 (type In-row data). Page (1:2839352) is missing a reference from previous page (1:3598023). Possible chain linkage problem. Repairing this error requires other errors to be corrected first. Msg 8928, Level 16, State 1, Line 1 Object ID 477960779, index ID 3, partition ID 72057594074890240, alloc unit ID 72057594081509376 (type In-row data): Page (1:3598023) could not be processed. See other errors for details. The repair level on the DBCC statement caused this repair to be bypassed. Msg 8939, Level 16, State 98, Line 1 Table error: Object ID 477960779, index ID 3, partition ID 72057594074890240, alloc unit ID 72057594081509376 (type In-row data), page (1:3598023). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 213911561 and -4. Repairing this error requires other errors to be corrected first. Msg 8976, Level 16, State 1, Line 1 Table error: Object ID 477960779, index ID 3, partition ID 72057594074890240, alloc unit ID 72057594081509376 (type In-row data). Page (1:3598023) was not seen in the scan although its parent (1:7723523) and previous (1:7723545) refer to it. Check any previous errors. Repairing this error requires other errors to be corrected first. Msg 8928, Level 16, State 1, Line 1 Object ID 477960779, index ID 3, partition ID 72057594074890240, alloc unit ID 72057594081509376 (type In-row data): Page (1:3628311) could not be processed. See other errors for details. Repairing this error requires other errors to be corrected first. Msg 8939, Level 16, State 98, Line 1 Table error: Object ID 477960779, index ID 3, partition ID 72057594074890240, alloc unit ID 72057594081509376 (type In-row data), page (1:3628311). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12584969 and -4. Repairing this error requires other errors to be corrected first. Msg 8976, Level 16, State 1, Line 1 Table error: Object ID 477960779, index ID 3, partition ID 72057594074890240, alloc unit ID 72057594081509376 (type In-row data). Page (1:3628311) was not seen in the scan although its parent (1:13500023) and previous (1:3075648) refer to it. Check any previous errors.
2. Try again,Try running lost data fixselect object_name(477960779) - Find fault objects according to Object_ID
use db_tank
SELECT Count (1) from db_tank..sys_users_goods where meansxist = 1 --61364953 - Back up the valid data of the library, record the valid data line of the table
select count(1) From db_tank..sys_users_goods - actually an error, then it is definitely ISEXIST! = 1 data where the data is located, then even if the data is lost, it is ISEXIST! = 1, that is, I don't care. Invalid data. So directly run
dbcc checktable('Sys_Users_Goods', REPAIR_ALLOW_DATA_LOSS - Try to run lost data fix - Error Has Been
repaired;
Select Count (1) from db_tank..sys_users_goods where meansxist = 1 - 61364953 - The check data is equal to 61364953, finds equal, prove that only non-valid data is lost
SELECT Count (1) from db_tank..sys_users_goods - View again, do it complete the repair, one check, no report, then proof the error has been fixed.- Restore database mode for multi-user mode
alter database db_tank
set multi_user with rollback IMMEDIATE
DBCC CHECKDB is the most common command that administers is also the command that must be known. Renewal of regular inspections and problems is more important! ! Here is some basic usage of DBCC CHECKDB.
Note: Data loss caused by using the repair_allow_data_loss parameter may not be accepted, and the data loss from the backup restore can be done in the heart, and the number of data clauses before the query before the data bar is compared to the number of data behind the number of data. In addition, try to retrieve in early backups.
Although SQLServer has made some optimizations for DBCC Checkdb but for larger databases or unclear balances, different CHECK checks is performed to disperse the impact of Check. You can also reduce some consumption burden by the following two parameters.
Hello,
After a brief network outage, I found some consistency errors in 600GB document database after running DBCC CHECKDB.
Output of the command is as follows:
«Msg 2533, Level 16, State 2, Line 1 Table error: page (5:17310848) allocated to object ID 347227865, index ID 1, partition ID 72057710633091072, alloc unit ID 72057710638792704 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header. The repair level on the DBCC statement caused this repair to be bypassed. Msg 8980, Level 16, State 1, Line 1 Table error: Object ID 347227865, index ID 1, partition ID 72057710633091072, alloc unit ID 72057710638792704 (type In-row data). Index node page (0:0), slot 0 refers to child page (5:17310848) and previous child (0:0), but they were not encountered. Repairing this error requires other errors to be corrected first. CHECKDB found 0 allocation errors and 2 consistency errors in table ‘sys.ifts_comp_fragment_101575400_1779051’ (object ID 347227865). Msg 8978, Level 16, State 1, Line 1 Table error: Object ID 427228150, index ID 1, partition ID 72057710633418752, alloc unit ID 72057710639120384 (type In-row data). Page (3:71538001) is missing a reference from previous page (5:17576290). Possible chain linkage problem. Repairing this error requires other errors to be corrected first. Msg 8978, Level 16, State 1, Line 1 Table error: Object ID 427228150, index ID 1, partition ID 72057710633418752, alloc unit ID 72057710639120384 (type In-row data). Page (4:8378242) is missing a reference from previous page (5:17950741). Possible chain linkage problem. Repairing this error requires other errors to be corrected first. Msg 2533, Level 16, State 2, Line 1 Table error: page (5:17576290) allocated to object ID 427228150, index ID 1, partition ID 72057710633418752, alloc unit ID 72057710639120384 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header. The repair level on the DBCC statement caused this repair to be bypassed. Msg 8976, Level 16, State 1, Line 1 Table error: Object ID 427228150, index ID 1, partition ID 72057710633418752, alloc unit ID 72057710639120384 (type In-row data). Page (5:17576290) was not seen in the scan although its parent (4:7810205) and previous (3:71538000) refer to it. Check any previous errors. Repairing this error requires other errors to be corrected first. Msg 2533, Level 16, State 2, Line 1 Table error: page (5:17950741) allocated to object ID 427228150, index ID 1, partition ID 72057710633418752, alloc unit ID 72057710639120384 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header. Repairing this error requires other errors to be corrected first. Msg 8976, Level 16, State 1, Line 1 Table error: Object ID 427228150, index ID 1, partition ID 72057710633418752, alloc unit ID 72057710639120384 (type In-row data). Page (5:17950741) was not seen in the scan although its parent (4:7810205) and previous (1:4596995) refer to it. Check any previous errors. Repairing this error requires other errors to be corrected first. CHECKDB found 0 allocation errors and 6 consistency errors in table ‘sys.ifts_comp_fragment_101575400_1779056’ (object ID 427228150). Msg 2533, Level 16, State 2, Line 1 Table error: page (5:18233724) allocated to object ID 779229404, index ID 1, partition ID 72057710634860544, alloc unit ID 72057710640562176 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header. The repair level on the DBCC statement caused this repair to be bypassed. Msg 8980, Level 16, State 1, Line 1 Table error: Object ID 779229404, index ID 1, partition ID 72057710634860544, alloc unit ID 72057710640562176 (type In-row data). Index node page (0:0), slot 0 refers to child page (5:18233724) and previous child (0:0), but they were not encountered. Repairing this error requires other errors to be corrected first. CHECKDB found 0 allocation errors and 2 consistency errors in table ‘sys.ifts_comp_fragment_101575400_1779078’ (object ID 779229404). CHECKDB found 0 allocation errors and 10 consistency errors in database ‘Database_x’. repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Database_x, repair_rebuild).»
If I do a select for all the object ID’s (there’s 3 unique ones), I get following results:
Select object_name(427228150) Result: ifts_comp_fragment_101575400_1779056
Select object_name(347227865) Result: ifts_comp_fragment_101575400_1779051
Select object_name(779229404) ifts_comp_fragment_101575400_1779078
To me it seems all the corruption is in search index. Is it possible to estimate the amount and type of lost data from this?
SQL Server version is MS SQL Server 2008 R2 with latest service packs.