Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
toeho
Starting Member
2 Posts |
Posted - 2005-11-21 : 17:23:40
|
I have a database that has a consistency error. When I run a DBCC CHECKDB WITH NO_INFOMSGS, ALL_ERRORMSGS I get the following.Server: Msg 8929, Level 16, State 1, Line 1Object ID 2: Errors found in text ID 72205074432 owned by data record identified by RID = (1:1944:23) id = 1216723387 and indid = 6.Server: Msg 8961, Level 16, State 1, Line 1Table error: Object ID 2. The text, ntext, or image node at page (1:62963), slot 49, text ID 72188297216 does not match its reference from page (1:1944), slot 23.CHECKDB found 0 allocation errors and 2 consistency errors in table 'sysindexes' (object ID 2).CHECKDB found 0 allocation errors and 2 consistency errors in database 'JDE_PDBANDIT_TEST'.If I run a DBCC CHECKDB ('JDE_PDBANDIT_TEST', REPAIR_ALLOW_DATA_LOSS)I get the followingServer: Msg 8929, Level 16, State 1, Line 1Object ID 2: Errors found in text ID 72205074432 owned by data record identified by RID = (1:1944:23) id = 1216723387 and indid = 6.Server: Msg 8961, Level 16, State 1, Line 1Table error: Object ID 2. The text, ntext, or image node at page (1:62963), slot 49, text ID 72188297216 does not match its reference from page (1:1944), slot 23.DBCC results for 'JDE_PDBANDIT_TEST'.DBCC results for 'sysobjects'.There are 4707 rows in 64 pages for object 'sysobjects'.DBCC results for 'sysindexes'. 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.There are 6811 rows in 477 pages for object 'sysindexes'.Can anyone provide any other avenues to try and resolve this issue. |
|
toeho
Starting Member
2 Posts |
Posted - 2005-11-21 : 17:24:58
|
FYI - We are running SQL2000 SP4 on Windows 2003 SP1 serverThanks |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2005-11-21 : 17:47:04
|
The stats blob for index id 6 of object 1216723387 is corrupt. You should be able to fix this by dropping and recreating the stats for that index. The index could be hypothetical (from running the index tuning wizard) in which case you can just drop the index.Why did you run REPAIR_ALLOW_DATA_LOSS if you don't know what this error is? Do you have a sensible backup strategy for if something more serious happens in future?Paul RandalLead Program Manager, Microsoft SQL Server Storage Engine(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.) |
|
|
|
|
|
|
|