CHECKDB: 97 Consistency Errors And None Repaired

Hi all,

I'm using WSUS2 to deploy software updates at my company, WSUS2 uses WMSDE (SQL Server Desktop Engine 2000 SP4) to store its database.

WSUS2 suddenly stopped working, I identified problems at the Database Log reading like this:

quote:
2006-05-11 12:17:52.64 spid54 Error: 7105, Severity: 22, State: 6
2006-05-11 12:17:52.64 spid54 Page (1:79), slot 29 for text, ntext, or image node does not exist..
[...]


So I ran a CHECKDB via osql on the commandline and got errors which should be repaired with a minimum of REPAIR_ALLOW_DATA_LOSS.

So I ran the following command on the corruprt Datebase 'SUSDB' after putting the DB into single user mode:


1> DBCC CHECKDB ('SUSDB',REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS
2> GO


And I got the fowllowing output (condensed):

quote:
Msg 8929, Level 16, State 1, Server FILESWSUS, Line 1
Object ID 2: Errors found in text ID 131203072 owned by data record identified
by RID = (1:24:2) id = 1 and indid = 3.
Msg 8929, Level 16, State 1, Server FILESWSUS, Line 1
Object ID 2: Errors found in text ID 131268608 owned by data record identified
by RID = (1:24:6) id = 3 and indid = 2.
Msg 8929, Level 16, State 1, Server FILESWSUS, Line 1
Object ID 2: Errors found in text ID 131334144 owned by data record identified
by RID = (1:24:7) id = 4 and indid = 1.
Msg 8929, Level 16, State 1, Server FILESWSUS, Line 1
Object ID 2: Errors found in text ID 131399680 owned by data record identified
by RID = (1:24:8) id = 4 and indid = 2.
Msg 8929, Level 16, State 1, Server FILESWSUS, Line 1
Object ID 2: Errors found in text ID 131465216 owned by data record identified
by RID = (1:24:13) id = 10 and indid = 2.
Msg 8929, Level 16, State 1, Server FILESWSUS, Line 1
Object ID 2: Errors found in text ID 131530752 owned by data record identified
by RID = (1:24:15) id = 11 and indid = 1.

[... MANY MANY MORE OF THOSE FAILURES WITH DIFFERENT IDs ...]

Object ID 2: Errors found in text ID 459538432 owned by data record identified
by RID = (1:104:27) id = 1858105660 and indid = 3.
The repair level on the DBCC statement caused this repair to be
bypassed.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
Msg 8929, Level 16, State 1, Server FILESWSUS, Line 1
Object ID 2: Errors found in text ID 459735040 owned by data record identified
by RID = (1:104:28) id = 1858105660 and indid = 4.
Msg 8929, Level 16, State 1, Server FILESWSUS, Line 1
Object ID 2: Errors found in text ID 4462411776 owned by data record identified
by RID = (1:107:5) id = 373576369 and indid = 6.
Msg 8929, Level 16, State 1, Server FILESWSUS, Line 1
Object ID 2: Errors found in text ID 327745536 owned by data record identified
by RID = (1:107:10) id = 487672785 and indid = 1.

[... MANY MANY MORE OF THOSE FAILURES WITH DIFFERENT IDs ...]

Msg 8964, Level 16, State 1, Server FILESWSUS, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:64), slot
4, text ID 459735040 is not referenced.
Msg 8964, Level 16, State 1, Server FILESWSUS, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:68), slot
7, text ID 197459968 is not referenced.
Msg 8964, Level 16, State 1, Server FILESWSUS, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:69), slot
0, text ID 197263360 is not referenced.
Msg 8964, Level 16, State 1, Server FILESWSUS, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:70), slot
0, text ID 4462411776 is not referenced.
Msg 8964, Level 16, State 1, Server FILESWSUS, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:71), slot
5, text ID 197197824 is not referenced.
Msg 8928, Level 16, State 1, Server FILESWSUS, Line 1
Object ID 2, index ID 255: Page (1:79) could not be processed. See other errors
for details.
Msg 8965, Level 16, State 1, Server FILESWSUS, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:79), slot
0, text ID 327745536 is referenced by page (1:107), slot 10, but was not seen
in the scan.

[... MANY MANY MORE OF THOSE FAILURES WITH DIFFERENT IDs ...]

The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
CHECKDB found 0 allocation errors and 97 consistency errors in table
'sysindexes' (object ID 2).
CHECKDB found 0 allocation errors and 97 consistency errors in database
'SUSDB'.


None of the errors are repaired, what can I do to repair the Database?

Thanks for any hints!

http://www.linuxhelpforum.de