Insert operation fell

Hi,
I had an application trying to insert a row into a table
and fell with the following error msg which I have copied
bellow.
I joined sysobjects and sysindexes on the id column which
is ID of the table to which the index belongs and filtered
by the table name and find that there are 15 rows in
sysindexes for the table (indid from 1 to 15). This comes
in line with the outcome of sp_helpindex. I also verified
that the given id does not belong to other object in the
db.
I fell to understand why the insert operation was trying
to update indid 21 that does not exist and should not exist
--CHECKTABLE on sysindexes found nothing to correct.
Error: 602, Severity: 21, State: 13
Could not find row in sysindexes for database ID 7, object
ID 1798349521, index ID 21. Run DBCC CHECKTABLE on
sysindexes.
DBSRVR - FAILED in Execute S1000 602
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not
find row in sysindexes for database ID 7, object ID
1798349521, index ID 21. Run DBCC CHECKTABLE on sysindexes.
Thanks,
Yaniv
Try to rebuild all table indexes - think this would help
"Yaniv" <anonymous@.discussions.microsoft.com> wrote in message
news:b37f01c43738$eb688b90$a501280a@.phx.gbl...
> Hi,
> I had an application trying to insert a row into a table
> and fell with the following error msg which I have copied
> bellow.
> I joined sysobjects and sysindexes on the id column which
> is ID of the table to which the index belongs and filtered
> by the table name and find that there are 15 rows in
> sysindexes for the table (indid from 1 to 15). This comes
> in line with the outcome of sp_helpindex. I also verified
> that the given id does not belong to other object in the
> db.
> I fell to understand why the insert operation was trying
> to update indid 21 that does not exist and should not exist
> --CHECKTABLE on sysindexes found nothing to correct.
>
> Error: 602, Severity: 21, State: 13
> Could not find row in sysindexes for database ID 7, object
> ID 1798349521, index ID 21. Run DBCC CHECKTABLE on
> sysindexes.
> DBSRVR - FAILED in Execute S1000 602
> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not
> find row in sysindexes for database ID 7, object ID
> 1798349521, index ID 21. Run DBCC CHECKTABLE on sysindexes.
|||It seems you have some corruption (inconsistency) in the database:
http://www.karaszi.com/SQLServer/inf...suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Yaniv" <anonymous@.discussions.microsoft.com> wrote in message news:b37f01c43738$eb688b90$a501280a@.phx.gbl...
> Hi,
> I had an application trying to insert a row into a table
> and fell with the following error msg which I have copied
> bellow.
> I joined sysobjects and sysindexes on the id column which
> is ID of the table to which the index belongs and filtered
> by the table name and find that there are 15 rows in
> sysindexes for the table (indid from 1 to 15). This comes
> in line with the outcome of sp_helpindex. I also verified
> that the given id does not belong to other object in the
> db.
> I fell to understand why the insert operation was trying
> to update indid 21 that does not exist and should not exist
> --CHECKTABLE on sysindexes found nothing to correct.
>
> Error: 602, Severity: 21, State: 13
> Could not find row in sysindexes for database ID 7, object
> ID 1798349521, index ID 21. Run DBCC CHECKTABLE on
> sysindexes.
> DBSRVR - FAILED in Execute S1000 602
> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not
> find row in sysindexes for database ID 7, object ID
> 1798349521, index ID 21. Run DBCC CHECKTABLE on sysindexes.
> Thanks,
> Yaniv
|||Thanks Alex, I would expect so but it is imoportant for me
to understand the cause to this behavior.

>--Original Message--
>Try to rebuild all table indexes - think this would help
>"Yaniv" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:b37f01c43738$eb688b90$a501280a@.phx.gbl...
copied[vbcol=seagreen]
which[vbcol=seagreen]
filtered[vbcol=seagreen]
comes[vbcol=seagreen]
verified[vbcol=seagreen]
exist[vbcol=seagreen]
object[vbcol=seagreen]
sysindexes.
>
>.
>
|||I think it's some hardware error when writing index trees to disk... even
best of the best may have faults, and not the men only but this creatures of
iron too. The only other cause is rare MSSQL software error - contact vendor
with details, maybe they'll find appropriate record in knowledge base
<anonymous@.discussions.microsoft.com> wrote in message
news:b50d01c4375d$105468b0$a001280a@.phx.gbl...[vbcol=seagreen]
> Thanks Alex, I would expect so but it is imoportant for me
> to understand the cause to this behavior.
>
>
> message
> copied
> which
> filtered
> comes
> verified
> exist
> object
> sysindexes.
|||Thanks agaian.

>--Original Message--
>I think it's some hardware error when writing index trees
to disk... even
>best of the best may have faults, and not the men only
but this creatures of
>iron too. The only other cause is rare MSSQL software
error - contact vendor
>with details, maybe they'll find appropriate record in
knowledge base[vbcol=seagreen]
><anonymous@.discussions.microsoft.com> wrote in message
>news:b50d01c4375d$105468b0$a001280a@.phx.gbl...
me[vbcol=seagreen]
help[vbcol=seagreen]
table[vbcol=seagreen]
the[vbcol=seagreen]
trying[vbcol=seagreen]
not
>
>.
>