March 30, 2006 at 2:06 pm
Hello,
I recieved the following error when I ran the Check DB command. In the past when I have had corruption in the sysindexes table, I have had to create a brand new DB and DTS the information from the corrupt db into the new one. I would hate to have to do this at this time, but running checkdb with repair_allow_data_loss on a system table does not sound like a great idea to me either. Any suggestions?
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 451608576 owned by data record identified by RID = (1:2213:19) id = 1207675350 and indid = 6.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:5686), slot 1, text ID 451608576 is referenced by page (1:4662), slot 89, but was not seen in the scan.
DBCC results for 'sysindexes'.
There are 1758 rows in 64 pages for object 'sysindexes'.
CHECKTABLE found 0 allocation errors and 2 consistency errors in table 'sysindexes' (object ID 2).
March 31, 2006 at 7:04 am
Dave,
have you tried running DBCC CHECKALLOC ? In my experience errors in checkdb are most of the time related to disk errors.
Also at http://www.sqlfe.com/ you find a utility which enables you to read the data on the page in question. You can that copy that data before you run DBCC CHECDB with repair_allow_data_loss. Although I'm not sure if it will help in your case since it looks like it's a page containg text/image data.
Markus
[font="Verdana"]Markus Bohse[/font]
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply