Добро пожаловать в форум, Guest  >>   Войти | Регистрация | Поиск | Правила | В избранное | Подписаться
Все форумы / Microsoft SQL Server Новый топик    Ответить
 проблема с базой 1с  [new]
sergeysam
Member

Откуда:
Сообщений: 1
Здравствуйте.

Возникла проблема с базой 1с 8.1

Microsoft SQL Server 2005 - 9.00.4053.00 (X64) May 26 2009 14:13:01 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)

Обнаружили, к большому сожалению поздно, последний бэкап месячной давности.

Что проверели:

+ DBCC CHECKDB with PHYSICAL_ONLY

DBCC CHECKDB with PHYSICAL_ONLY

DBCC results for 'msk-work'.
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:2493783) with latch type SH. 1117(error not found) failed.
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:2493786) with latch type SH. 1117(error not found) failed.
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:2493792) with latch type SH. 1117(error not found) failed.
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:2493793) with latch type SH. 1117(error not found) failed.
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:2493794) with latch type SH. 1117(error not found) failed.
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:2493795) with latch type SH. 1117(error not found) failed.
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:2493796) with latch type SH. 1117(error not found) failed.
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:2493797) with latch type SH. 1117(error not found) failed.
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:2493798) with latch type SH. 1117(error not found) failed.
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 (1:2493882) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493883) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493884) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493885) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493886) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493887) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493888) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493889) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493890) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493891) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493892) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493893) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493894) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493895) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493896) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493899) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493900) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493901) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493902) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493903) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493906) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493908) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493909) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
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 (1:2493910) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
CHECKDB found 0 allocation errors and 33 consistency errors not associated with any single object.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:2493786) allocated to object ID 339584348, index ID 2, partition ID 72057595871756288, alloc unit ID 72057595701231616 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
CHECKDB found 0 allocation errors and 1 consistency errors in table '_InfoReg20116' (object ID 339584348).
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:2493783) allocated to object ID 1095727006, index ID 1, partition ID 72057595546370048, alloc unit ID 72057595377025024 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 8928, Level 16, State 1, Line 1
Object ID 1095727006, index ID 3, partition ID 72057595546501120, alloc unit ID 72057595377156096 (type In-row data): Page (1:2493896) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1095727006, index ID 3, partition ID 72057595546501120, alloc unit ID 72057595377156096 (type In-row data): Page (1:2493899) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1095727006, index ID 3, partition ID 72057595546501120, alloc unit ID 72057595377156096 (type In-row data): Page (1:2493900) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1095727006, index ID 3, partition ID 72057595546501120, alloc unit ID 72057595377156096 (type In-row data): Page (1:2493901) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1095727006, index ID 3, partition ID 72057595546501120, alloc unit ID 72057595377156096 (type In-row data): Page (1:2493902) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1095727006, index ID 3, partition ID 72057595546501120, alloc unit ID 72057595377156096 (type In-row data): Page (1:2493903) could not be processed. See other errors for details.
CHECKDB found 0 allocation errors and 7 consistency errors in table '_AccumRegTotals17916' (object ID 1095727006).
Msg 8928, Level 16, State 1, Line 1
Object ID 1388636090, index ID 1, partition ID 72057595985264640, alloc unit ID 72057595817820160 (type In-row data): Page (1:2493906) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1388636090, index ID 1, partition ID 72057595985264640, alloc unit ID 72057595817820160 (type In-row data): Page (1:2493908) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1388636090, index ID 1, partition ID 72057595985264640, alloc unit ID 72057595817820160 (type In-row data): Page (1:2493909) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1388636090, index ID 1, partition ID 72057595985264640, alloc unit ID 72057595817820160 (type In-row data): Page (1:2493910) could not be processed. See other errors for details.
CHECKDB found 0 allocation errors and 4 consistency errors in table '_AccumRegTotals20612' (object ID 1388636090).
Msg 8928, Level 16, State 1, Line 1
Object ID 1406680109, index ID 1, partition ID 72057595352055808, alloc unit ID 72057595182710784 (type In-row data): Page (1:2493881) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1406680109, index ID 1, partition ID 72057595352055808, alloc unit ID 72057595182710784 (type In-row data), page (1:2493881). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 79824905 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 1406680109, index ID 1, partition ID 72057595352055808, alloc unit ID 72057595182710784 (type In-row data): Page (1:2493882) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1406680109, index ID 1, partition ID 72057595352055808, alloc unit ID 72057595182710784 (type In-row data): Page (1:2493883) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1406680109, index ID 1, partition ID 72057595352055808, alloc unit ID 72057595182710784 (type In-row data): Page (1:2493884) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1406680109, index ID 1, partition ID 72057595352055808, alloc unit ID 72057595182710784 (type In-row data): Page (1:2493885) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1406680109, index ID 1, partition ID 72057595352055808, alloc unit ID 72057595182710784 (type In-row data): Page (1:2493886) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1406680109, index ID 1, partition ID 72057595352055808, alloc unit ID 72057595182710784 (type In-row data): Page (1:2493887) could not be processed. See other errors for details.
CHECKDB found 0 allocation errors and 8 consistency errors in table '_InfoReg16648' (object ID 1406680109).
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:2493792) allocated to object ID 1788637515, index ID 1, partition ID 72057595991687168, alloc unit ID 72057595824898048 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:2493793) allocated to object ID 1788637515, index ID 1, partition ID 72057595991687168, alloc unit ID 72057595824898048 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:2493794) allocated to object ID 1788637515, index ID 1, partition ID 72057595991687168, alloc unit ID 72057595824898048 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:2493795) allocated to object ID 1788637515, index ID 1, partition ID 72057595991687168, alloc unit ID 72057595824898048 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:2493796) allocated to object ID 1788637515, index ID 1, partition ID 72057595991687168, alloc unit ID 72057595824898048 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:2493797) allocated to object ID 1788637515, index ID 1, partition ID 72057595991687168, alloc unit ID 72057595824898048 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:2493798) allocated to object ID 1788637515, index ID 1, partition ID 72057595991687168, alloc unit ID 72057595824898048 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
CHECKDB found 0 allocation errors and 7 consistency errors in table '_AccumReg18964' (object ID 1788637515).
Msg 8928, Level 16, State 1, Line 1
Object ID 2048114437, index ID 1, partition ID 72057595951906816, alloc unit ID 72057595785183232 (type In-row data): Page (1:2493888) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 2048114437, index ID 1, partition ID 72057595951906816, alloc unit ID 72057595785183232 (type In-row data): Page (1:2493889) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 2048114437, index ID 1, partition ID 72057595951906816, alloc unit ID 72057595785183232 (type In-row data): Page (1:2493890) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 2048114437, index ID 1, partition ID 72057595951906816, alloc unit ID 72057595785183232 (type In-row data): Page (1:2493891) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 2048114437, index ID 1, partition ID 72057595951906816, alloc unit ID 72057595785183232 (type In-row data): Page (1:2493892) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 2048114437, index ID 1, partition ID 72057595951906816, alloc unit ID 72057595785183232 (type In-row data): Page (1:2493893) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 2048114437, index ID 1, partition ID 72057595951906816, alloc unit ID 72057595785183232 (type In-row data): Page (1:2493894) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 2048114437, index ID 1, partition ID 72057595951906816, alloc unit ID 72057595785183232 (type In-row data): Page (1:2493895) could not be processed. See other errors for details.
CHECKDB found 0 allocation errors and 8 consistency errors in table '_Document507_VT12287' (object ID 2048114437).
CHECKDB found 0 allocation errors and 68 consistency errors in database 'msk-work'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (msk-work).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.



Полный dbcc checkdb больше 7 тыс строк, в конце

CHECKDB found 0 allocation errors and 147 consistency errors in database 'msk-work'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (msk-work)

Особенно смущают ошибки SH. В итоге выяснили что есть ошибки в файловой системе:

+ chkdsk

The type of the file system is NTFS.
Volume label is 1c.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
1168 file records processed.
File verification completed.
33 large file records processed.
0 bad file records processed.
0 EA records processed.
0 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
3909 index entries processed.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.


Бэкап сейчас не снять, ругается на ошибку чтения. Файл при остановленном сервисе sql тоже не копируется, похоже из-за ошибок в файловой системе.
В месячном бэкапе ошибок нет.

Соответственно, видется несколько выходов из ситуации, на живой базе:

1) запустить chkdsk /f, может помочь? или наоборот поламает всю базу?
2) dbcc с параметром repair_allow_data_loss, насколько все может поламаться?
3) запустить тестирование и восстановление в самой программе 1с
4) пытать перелить таблицы, которые пока читаются в рабочей базе
5) пытаться слить таблицы из бэкапа и текущей базы

Спасибо за советы.
26 июл 11, 22:29    [11030975]     Ответить | Цитировать Сообщить модератору
 Re: проблема с базой 1с  [new]
alexeyvg
Member

Откуда: Moscow
Сообщений: 31965
sergeysam
2) dbcc с параметром repair_allow_data_loss, насколько все может поламаться?
3) запустить тестирование и восстановление в самой программе 1с
4) пытать перелить таблицы, которые пока читаются в рабочей базе
5) пытаться слить таблицы из бэкапа и текущей базы
Думаю, это не поможет, если даже файловая система файла не понимает.
sergeysam
Обнаружили, к большому сожалению поздно, последний бэкап месячной давности.
Ответственного за бакапы уже уволили? :-)
26 июл 11, 23:00    [11031066]     Ответить | Цитировать Сообщить модератору
 Re: проблема с базой 1с  [new]
Raoul
Member

Откуда:
Сообщений: 177
sergeysam,

Cитуация тяжелая, похоже, диск начал сыпаться. Я бы в этой ситуации прекратил мучать диск попытками исправить БД, загрузиться c LiveCD или другого носителя и попробовал спасти файлы БД чем-нибудь типа TestDisk или DiskGetor, чтобы потом уже на заведомо исправном диске приаттачить их и попытаться починить.
27 июл 11, 12:35    [11033229]     Ответить | Цитировать Сообщить модератору
 Re: проблема с базой 1с  [new]
Raoul
Member

Откуда:
Сообщений: 177
Да, ни в коем случае не нужно делать chkdsk и тому подобное. Каждое лишнее обращение к сыплющемуся диску уменьшает шансы что-то с него скопировать. Грузимся с другого носителя и спасаем все, что можно, в порядке убывания важности.
27 июл 11, 12:39    [11033263]     Ответить | Цитировать Сообщить модератору
Все форумы / Microsoft SQL Server Ответить