error:8646,severity:21,state:1

hi to all
Does any one here help me please in this error.By the way i've found this
error when i check the error log due to error in my replication monitor,all
subscriber cannot replicate due to this error.Im using sql 7.
complete error:
the index entry for row ID was not found in index Id 5,of table 362536425,
in Database 'Database Name'
Error:8646,Severity:21,State:1
Thank you in advance
Pheter R. Flores
This article applies to SQL2000, but I'd check to see if it apples to SQL7
anyway:
http://support.microsoft.com/default.aspx?scid=kb;en-us;822747
I'd also run DBB CHECKDB (even though the article says DBCC will not report
any errors described by the article), especially if the KB article doesn't
apply.
For a non-clustered index, often dropping and re-creating it may fix the
problem, though not the root cause.
Linchi
"MICS" wrote:

> hi to all
> Does any one here help me please in this error.By the way i've found this
> error when i check the error log due to error in my replication monitor,all
> subscriber cannot replicate due to this error.Im using sql 7.
> complete error:
> the index entry for row ID was not found in index Id 5,of table 362536425,
> in Database 'Database Name'
> Error:8646,Severity:21,State:1
> Thank you in advance
> Pheter R. Flores
|||I had already read that article before and it seems that the fix is only
applied on sql 2000.Is there any fix aside from the hotfix on that article?
Thank you so much
"Linchi Shea" wrote:
[vbcol=seagreen]
> This article applies to SQL2000, but I'd check to see if it apples to SQL7
> anyway:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;822747
> I'd also run DBB CHECKDB (even though the article says DBCC will not report
> any errors described by the article), especially if the KB article doesn't
> apply.
> For a non-clustered index, often dropping and re-creating it may fix the
> problem, though not the root cause.
> Linchi
> "MICS" wrote:
|||maybe your right,but the problem is i don't know what particular table should
i rebuild the index,because as you've notice the error message display only
the number of the table and not the name.Do you know hoe to locate the table
name given only the number?thanks
"Tibor Karaszi" wrote:

> Seems like a corruption problem. Possibly dropping that index (and then re-creating it) will clean
> it up. Also see http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "MICS" <MICS@.discussions.microsoft.com> wrote in message
> news:EA0291E2-D243-4896-A0F8-CCCD06923FF9@.microsoft.com...
>
|||i''ve found it on the sysobjects system table,and by the way i already solve
the problem by running dbcc.tnank you so much
"Tibor Karaszi" wrote:

> Check out the OBJECT_NAME() function. Or look it up in the sysobjects system table.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "MICS" <MICS@.discussions.microsoft.com> wrote in message
> news:46BA4D55-694E-4428-9A1D-F23813F4FC7A@.microsoft.com...
>