Post reply

Database error message in SQL log files

  • February 24, 2006 at 7:52 pm

    #96664

    I am attempting to identitfy what is causing the following error in the SQL Server logs in SQL 2000 every hour:

    Error: 8908, Severity: 22, State: 6

    Table error: Database ID 9, object ID 2043154324, index ID 0. Chain linkage mismatch. (1:337518)->next = (1:337519), but (1:337519)->prev = (1:337515).

    The only similar reference I have located so far mentions to apply SP4. I have done this, however, the error message is different from what is on the Microsoft Knowledge Base. What command can I run in Query Analyzer to find which Database has the ID of 9? Any assistance would be greatly appreciated.

    Thanks in advance for any advice you can give.

    Stephen

  • February 27, 2006 at 12:33 am

    #623398

    select db_name(9)

    => After getting the database name, please run DBCC CHECKDB('DB_Name_Here')

    and let us know the result

    also please run

    select object_name(2043154324) in DBID 9

    to get object name.

  • February 27, 2006 at 12:19 pm

    #623519

    Thank you for your reply.  I ran the query you listed and have identified the database that is causing the error logs in SQL server. I ran DBCC CHECKDB but did not post it since I was not sure if you want such a long resultset. I have listed below the results of the "select object_name(2043154324)" query:

    DBCC results for 'SESSIONS'.

    There are 50706 rows in 971 pages for object 'SESSIONS'.

    CHECKDB found 0 allocation errors and 13 consistency errors in table 'SESSIONS' (object ID 2043154324).

    What should be my next step to resolving this issue? FYI, I am a parttime DBA (at best) so please excuse my lack of knowledge of what commands and sp I should run. Your assistance is greatly appreciated.

    Thanks again in advance for your assistance.

    Stephen

     

  • February 27, 2006 at 3:10 pm

    #623555

    You need to repair consistency errors.

    Try the NO DATA LOSS OPTIONS FIRST of the dbcc checkdb.

     

    example:

     dbcc checkdb ('DatabaseName', REPAIR_FAST)

    if still reports errors then:

    dbcc checkdb ('DatabaseName', REPAIR_REBUILD)

    and hopefully you will never need:

    dbcc checkdb ('DatabaseName', REPAIR_ALLOW_DATA_LOSS)

     

    you could use dbcc checktable instead but checkdb is the safest method (and you dont need for the moment to get any deeper into this )

    Good Luck

     


    * Noel

Viewing 4 posts - 1 through 3 (of 3 total)

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