Post reply

Index problem - Error: 8646, Severity: 21, State: 1

  • August 8, 2007 at 11:08 pm

    #61318

    Hi All,

    The sql server log of sql server 2000 with SP3 logs the following,

    Error: 8646, Severity: 21, State: 1

    The index entry for row ID  was not found

    in index ID 16, of table 966294502, in database

    I can find the corresponding the non clustered indesx and table name.

    I followed the article http://support.microsoft.com/kb/822747 and cannot able to find much on the error.

    I checked the integrity of the database, table, index and it is fine.

    and statistics of the index is also updated.

    DBCC SHOW_STATISTICS (tbs_t_Notification, ProcessState)

    Aug  9 2007 12:40PM  469279 22805 3 0.0 5.0

    The microsoft article states that the error is related to collation and please suggest how can I find the collation of the data in a table. I can find the collation of the database.

    Please advice me how can I trouble this index problem.

    Regards,

    Parthipan

  • August 9, 2007 at 6:01 am

    #725683

    Have you tried dropping the index and recreating it?

  • August 9, 2007 at 7:45 am

    #725714

    If you script out the table, you can see the collation.

    I'd maybe give a try to bcp out the table, just to be sure it's intact. That's usually been a good integrity test for me. If that works, I might try Clive's suggestion.

  • August 9, 2007 at 9:45 pm

    #725891

    Hi,

    I already rebuilded the index, updated the usage of sysindexes and also updated the statistics of the index.

    Please suggest me that the corresponding index should be manually dropped and recreated?

    Also enlighten me that BCP means importing the table and its structure to other database for safety purpose?

    I have checked the collation of the column in the table and it is having the same collation as the database with sort order 52 and not having the collation 'Latin1_General_BIN Collation' as mentioned in the MS article.

    So I cannot able to find the reason of occurence of this error.

    Please suggest me what could be the reason of this index error. Also we cannot upgrade the sql server service pack to SP4 for resolving it.

     

  • August 10, 2007 at 2:56 am

    #725925

    Morning,

    BCP (Bulk Copy Process) will export the data to another data source.  Steve suggested this to test the validity of the table and data.

    One other thing you could possibly try.  When you do this depends on when you can get downtime.

    1. Run a SELECT INTO to build a new table and copy the current data into the new table.

    2. Rename the existing table

    3. Rename the new table to the existing table.

    4. Create the indexes on the new table.

    See how that goes.

  • August 10, 2007 at 4:52 am

    #725944

    This a a know issue with the collation "Latin1_General_BIN Collation ".

    Please refer the following KB for FIX.http://support.microsoft.com/kb/822747/en-us

     

    Minaz

    "More Green More Oxygen !! Plant a tree today"

  • August 10, 2007 at 4:55 am

    #725945

    From the post you seem you have already followed the Kb and SP4 you will not be able to apply. Then try changing the collation and BCP out the data.

     

    Minaz

    "More Green More Oxygen !! Plant a tree today"

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply