Sergey21102
![](http://forum.ru-board.com/board/avatars/Cap'n Pete.gif)
Advanced Member | Редактировать | Профиль | Сообщение | ICQ | Цитировать | Сообщить модератору Похоже сломалась WSUS-овская база данных. в SQL Server Logs появились вот такие ошибки Код: 2007-06-07 15:16:51.31 spid64 Error: 7105, Severity: 22, State: 6 2007-06-07 15:16:51.31 spid64 Page (1:74208), slot 2 for text, ntext, or image node does not exist.. 2007-06-07 15:16:52.46 spid60 Error: 7105, Severity: 22, State: 6 2007-06-07 15:16:52.46 spid60 Page (1:74208), slot 2 for text, ntext, or image node does not exist.. 2007-06-07 15:16:52.82 spid62 Error: 7105, Severity: 22, State: 6 2007-06-07 15:16:52.82 spid62 Page (1:74208), slot 2 for text, ntext, or image node does not exist.. 2007-06-07 15:16:54.18 spid63 Error: 7105, Severity: 22, State: 6 2007-06-07 15:16:54.18 spid63 Page (1:74208), slot 2 for text, ntext, or image node does not exist.. 2007-06-07 15:17:40.37 spid60 Error: 7105, Severity: 22, State: 6 2007-06-07 15:17:40.37 spid60 Page (1:74208), slot 2 for text, ntext, or image node does not exist.. 2007-06-07 15:17:40.46 spid61 Error: 7105, Severity: 22, State: 6 2007-06-07 15:17:40.46 spid61 Page (1:74208), slot 2 for text, ntext, or image node does not exist.. | при проверке базы вылезают 4 ошибки, которые автоматом не лечаться Код: Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server 'EPCSERVER\FORDDB' as 'EPCSERVER\Àäìèíèñòðàòîð' (trusted) Starting maintenance plan 'DB Maintenance Plan1' on 07.06.2007 5:44:20 [1] Database SUSDB: Check Data and Index Linkage... [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8929: [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 1888725781: Errors found in text ID 127199215616 owned by data record identified by RID = (1:104847:4) EventOrdinalNUmber = 1681791. [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 1888725781: Errors found in text ID 127199281152 owned by data record identified by RID = (1:104847:4) EventOrdinalNUmber = 1681791. [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 1888725781. The text, ntext, or image node at page (1:74208), slot 2, text ID 127195152384 does not match its reference from page (1:104847), slot 4. [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 1888725781. The text, ntext, or image node at page (1:74208), slot 3, text ID 127195217920 does not match its reference from page (1:104847), slot 4. [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 4 consistency errors in table 'tbEventInstance' (object ID 1888725781). [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 4 consistency errors in database 'SUSDB'. [Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (SUSDB ). The following errors were found: [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 1888725781: Errors found in text ID 127199215616 owned by data record identified by RID = (1:104847:4) EventOrdinalNUmber = 1681791. [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 1888725781: Errors found in text ID 127199281152 owned by data record identified by RID = (1:104847:4) EventOrdinalNUmber = 1681791. [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 1888725781. The text, ntext, or image node at page (1:74208), slot 2, text ID 127195152384 does not match its reference from page (1:104847), slot 4. [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 1888725781. The text, ntext, or image node at page (1:74208), slot 3, text ID 127195217920 does not match its reference from page (1:104847), slot 4. [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 4 consistency errors in table 'tbEventInstance' (object ID 1888725781). [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 4 consistency errors in database 'SUSDB'. [Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (SUSDB ). ** Execution Time: 0 hrs, 0 mins, 40 secs ** End of maintenance plan 'DB Maintenance Plan1' on 07.06.2007 5:45:00 SQLMAINT.EXE Process Exit Code: 1 (Failed) | Есть ли возможность починить базу, а если нет как начать все с "чистого листа" ,хотя нет, не с совсем чистого, хотя бы имеющиеся обновления подцепить.. ЗЫ: база стоит на MS SQL 2000 EE sp4 WSUS версии 2, сборка 2.0.0.2620 Да, проявляется это только при синхронизации, перестала работать синхронизация и пишет "Последняя синхронизация: Никогда не выполнялась Результаты последней синхронизации:Н/Д" То есть потерялась и дата и факт синхронизации. |