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...
>

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. FloresThis 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:
> 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|||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...
> 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|||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...
> > 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
>|||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...
> 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...
>> > 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''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...
> > 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...
> >> > 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
> >>
>

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. FloresThis article applies to SQL2000, but I'd check to see if it apples to SQL7
anyway:
http://support.microsoft.com/defaul...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,al
l
> 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/defaul...kb;en-us;822747
> I'd also run DBB CHECKDB (even though the article says DBCC will not repor
t
> 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:
>|||Seems like a corruption problem. Possibly dropping that index (and then re-c
reating it) will clean
it up. Also see http://www.karaszi.com/SQLServer/in..._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...
> 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,al
l
> 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|||maybe your right,but the problem is i don't know what particular table shoul
d
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/in...ver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "MICS" <MICS@.discussions.microsoft.com> wrote in message
> news:EA0291E2-D243-4896-A0F8-CCCD06923FF9@.microsoft.com...
>|||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...[vbcol=seagreen]
> maybe your right,but the problem is i don't know what particular table sho
uld
> i rebuild the index,because as you've notice the error message display onl
y
> the number of the table and not the name.Do you know hoe to locate the tab
le
> name given only the number?thanks
> "Tibor Karaszi" wrote:
>|||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 syst
em 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...
>

Error:602,Severity:21,State:4

Hi,

In my application i used to do the take the backup of current

database and restore it with a backup which was taken earlier and

execute a select command on a particular table.

My problem is,backup & restore operations get completed

successfully but error is raised when tried to open a recordset

for a select statement.Following error was recorded in the sql

error log.

Error: 602, Severity: 21, State: 4

Could not find row in sysindexes for database ID 15, object ID

1109578991, index ID 1. Run DBCC CHECKTABLE on sysindexes..

After this i terminated my application and repeated the above

operation this time i got the same error but with index ID 0 but

the database id and object id remained the same.

When scanned the sysobjects for the particular objectid and i

found out that the id belong to a SP - dt_setpropertybyid_u

I have encountered the same problem three times,but after that i

did not get the problem

Regards

I would suggest running a CHECKDB on the database. If the database is too large find out which tables the query touches and run a CHECKTABLE on the those tables.

The following article could be helpful:

http://msdn2.microsoft.com/en-us/library/aa258727(SQL.80).aspx

http://msdn2.microsoft.com/en-us/library/aa258762(sql.80).aspx

HTH