[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1913
  • Last Modified:

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
0
Richard Comito
Asked:
Richard Comito
  • 3
  • 2
1 Solution
 
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
 
tigin44Commented:
it seems that one of your index pages has a corrupt page. You should fix by using this command...
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
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
 
dbidbaCommented:
If this is index corruption, it is safer to drop and recreate the index rather than to do DBCC repair.
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

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now