Error 644 Severity level 21

Hi,
I got the following error message for one of our databases:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 3/25/2005
Time: 9:18:53 AM
User: XXXXXXXX\Administrator
Computer: XXXXXX
Description:
Error: 644, Severity: 21, State: 3
Could not find the index entry for RID '16c42dc515100' in index page
(1:1725), index ID 0, database 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
I looked up the error in Books Online and it told me to run DBCC CHECKDB to
see the extent of the damage. It gave me the following result:
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'XXXXXXXXX_XXXXX_XXX_MSCRM', index
'sysobjects.ncsysobjects2' (ID 1) (index ID 3). Extra or invalid key for the
keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:155:91) with values (parent_obj = 1237579447 and id = 365243844) points to the data row identified by ().
DBCC results for 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
DBCC results for 'sysobjects'.
There are 2315 rows in 49 pages for object 'sysobjects'.
CHECKDB found 0 allocation errors and 1 consistency errors in table
'sysobjects' (object ID 1).
These don't seem to match. Should they?
The next thing that Books Online says to do is to run DBCC CHECKDB with the
REPAIR_REBUILD clause to fix the damage. Is this still an appropriate
course of action given that the error reported by checkdb doesn't seem to be
the one from the event log?
One of the other dba's here said that there may be a better way to rebuild
the index than to run the repair_rebuild on the entire database. I just
wanted to double check and get some other opinions/feedback before I
continued. Any help would really be appreciated. Thank you
-JohnHi
You have corruption.
Do a full backup of the database, then run the DBCC. There is probably more
than one problem so the DBCC finds the other one first.
At the same time, look for your backups because if the corruption is bad
enough, you need to restore to you last good backup.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"John Rosenlof" <greyseal96@.hotmail.com> wrote in message
news:O#0LBPYMFHA.3296@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I got the following error message for one of our databases:
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 3/25/2005
> Time: 9:18:53 AM
> User: XXXXXXXX\Administrator
> Computer: XXXXXX
> Description:
> Error: 644, Severity: 21, State: 3
> Could not find the index entry for RID '16c42dc515100' in index page
> (1:1725), index ID 0, database 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
> I looked up the error in Books Online and it told me to run DBCC CHECKDB
to
> see the extent of the damage. It gave me the following result:
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'XXXXXXXXX_XXXXX_XXX_MSCRM', index
> 'sysobjects.ncsysobjects2' (ID 1) (index ID 3). Extra or invalid key for
the
> keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:155:91) with values (parent_obj = 1237579447 and id => 365243844) points to the data row identified by ().
> DBCC results for 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
> DBCC results for 'sysobjects'.
> There are 2315 rows in 49 pages for object 'sysobjects'.
> CHECKDB found 0 allocation errors and 1 consistency errors in table
> 'sysobjects' (object ID 1).
> These don't seem to match. Should they?
> The next thing that Books Online says to do is to run DBCC CHECKDB with
the
> REPAIR_REBUILD clause to fix the damage. Is this still an appropriate
> course of action given that the error reported by checkdb doesn't seem to
be
> the one from the event log?
> One of the other dba's here said that there may be a better way to rebuild
> the index than to run the repair_rebuild on the entire database. I just
> wanted to double check and get some other opinions/feedback before I
> continued. Any help would really be appreciated. Thank you
> -John
>