How to trouble shoot a Possible Chain Linkage problem

I was checking my Job history and found this error that has been popping up when I run my nightly CHECKDB job.

Executed as user: NT AUTHORITY\SYSTEM. Table error: Object ID 631673298, index ID 1, partition ID 72057596144058368, alloc unit ID 72057596159852544 (type In-row data). The previous link (1:1086541) on page (1:160684) does not match the previous page (1:160685) that the parent (1:160683), slot 247 expects for this page. [SQLSTATE 42000] (Error 8935)  Table error: Object ID 631673298, index ID 1, partition ID 72057596144058368, alloc unit ID 72057596159852544 (type In-row data). Page (1:160684) is missing a reference from previous page (1:1086541). Possible chain linkage problem. [SQLSTATE 42000] (Error 8978)  Table error: Object ID 631673298, index ID 1, partition ID 72057596144058368, alloc unit ID 72057596159852544 (type In-row data). The previous link (1:160685) on page (1:1086542) does not match the previous page (1:160684) that the parent (1:160683), slot 248 expects for this page. [SQLSTATE 42000] (Error 8935)  DBCC results for 'impresario'. [SQLSTATE 01000] (Error 2536)  Service Broker Msg 9675, State

I am not sure what I should do to start and troubleshoot this issue.  Any suggestions would be helpful.

Thanks,

Gabicus
Richard ComitoDirector of ITAsked:
Who is Participating?
 
dbidbaConnect With a Mentor Commented:
If this is index corruption, it is safer to drop and recreate the index rather than to do DBCC repair.
0
 
tigin44Commented:
you should use the
DBCC CHECKDB
    ( 'database_name'
            [ , NOINDEX
                | { REPAIR_ALLOW_DATA_LOSS
                    | REPAIR_FAST
                    | REPAIR_REBUILD
                    } ]
    )    [ WITH { [ ALL_ERRORMSGS ]
                    [ , [ NO_INFOMSGS ] ]
                    [ , [ TABLOCK ] ]
                    [ , [ ESTIMATEONLY ] ]
                    [ , [ PHYSICAL_ONLY ] ]
                    }
        ]

cammand with correct parameters. ie..

DBCC CHECKDB
    ( 'database_name',  REPAIR_REBUILD )    
    WITH  ALL_ERRORMSGS
0
 
Richard ComitoDirector of ITAuthor Commented:
tigin44,

Thanks for the reply.  I am assuming that I should do this tonight when everyone is off the server and after I have done my Back Up?
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
tigin44Commented:
it seems that one of your index pages has a corrupt page. You should fix by using this command...
0
 
Richard ComitoDirector of ITAuthor Commented:
OK.  so this looks like I need to be in single user mode which means that I will need to do this when no one else is on.
0
 
Richard ComitoDirector of ITAuthor Commented:
not sure how to grade this.  I could not drop the index per say.  What I had to do is make a temp table export all the data to the temp table and re-import it back to the original table to make it re-index.  Any suggestions.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.