Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Chain Linkage mismatch error 8908

Posted on 2006-11-15
6
Medium Priority
?
2,124 Views
Last Modified: 2009-12-16
I have got the following error on SQL server 2000 SP 3a


Event Type:      Error
Event Source:      MSSQLSERVER
Event Category:      (2)
Event ID:      17052
Date:            15/Nov/2006
Time:            11:11:58
User:            N/A
Computer:      ZAJHBMUR-SQL01
Description:
Error: 8908, Severity: 22, State: 6
Table error: Database ID 7, object ID 73207461, index ID 6. Chain linkage mismatch. (3:1015910)->next = (3:1015911), but (3:1015911)->prev = (3:2659497).

I know which database it refers to but how can I find out which table it refers?

SQL server log shows the same reference.

I did dbcc checkdb which returned no errors.

It appears to be an index that is involved in which case I have read that a dbcc checktable repair_rebuild may fix the error. However I don't know which table to run it on.

Please advise
Mike Ward
0
Comment
Question by:MURSHIP
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2
6 Comments
 
LVL 6

Expert Comment

by:wtapsell
ID: 17946258
select
0
 
LVL 6

Expert Comment

by:wtapsell
ID: 17946270
Have you tried looking in the sysobjects table of the relevant database?
0
 
LVL 6

Accepted Solution

by:
wtapsell earned 2000 total points
ID: 17946285
For the relevant table:

select      *
from      sysobjects
where      id = 73207461


For the relevant index:

select      *
from      sysindexes
where      id = 73207461
and            indid = 6
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 

Author Comment

by:MURSHIP
ID: 17946350
Many thanks that worked I have the index name and table now.

If I drop the index and recreate it would this fix the error?

Regards
Mike
0
 
LVL 6

Expert Comment

by:wtapsell
ID: 17946826

That should work.
0
 

Author Comment

by:MURSHIP
ID: 17946843
Many thanks

Regards
0

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Recently we ran in to an issue while running some SQL jobs where we were trying to process the cubes.  We got an error saying failure stating 'NT SERVICE\SQLSERVERAGENT does not have access to Analysis Services. So this is a way to automate that wit…
An alternative to the "For XML" way of pivoting and concatenating result sets into strings, and an easy introduction to "common table expressions" (CTEs). Being someone who is always looking for alternatives to "work your data", I came across this …
This videos aims to give the viewer a basic demonstration of how a user can query current session information by using the SYS_CONTEXT function
Using examples as well as descriptions, and references to Books Online, show the documentation available for datatypes, explain the available data types and show how data can be passed into and out of variables.

721 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question