Could not find the index entry for RID 16abe380100 in index page (1:5269), index ID 0, database msdb..

Question

Post reply

Could not find the index entry for RID 16abe380100 in index page (1:5269), index ID 0, database msdb..

Robert Turner

SSC-Addicted

Points: 410
More actions
May 25, 2004 at 4:22 am

#65186

We are getting a lot of errors with the same message: Could not find the index entry for RID '16abe380100' in index page (1:5269), index ID 0, database 'msdb'..
What does the RID refer to?
How can I take the information in the error message and find the actual index or whatever is the problem?

Robert T Turner

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

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

Johan Bijnens SSC Guru Points: 135376 More actions · Answer 1

run DBCC CHECKDB ! see BOL

Johan

Learn to play, play to learn !

Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:

- How to post Performance Problems
- How to post data/code to get the best help[/url]

- How to prevent a sore throat after hours of presenting ppt

press F1 for solution, press shift+F1 for urgent solution 😀

Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me

kl-178476 Grasshopper Points: 15 More actions · Answer 2

What a completely useless answer!

Any Bozo could tell the guy to run DBCC, but what he asked was how to translate the error msg into something useful. The dbcc may very well find the index & table in question at the cost of several hours of slowing down the server while it runs. But when presented with an error message that appears to give the info needed, the natural question to ask is "what does this mean?"

If the answer is that the error msg doesn't contain enough info to identify the affected objects, why not say so. Or if you don't know the real answer, why bother providing an obvious but otherwise useless alternative?

Wesley Brown SSChampion Points: 12045 More actions · Answer 3

it means it went to look for a page it thought should have been there and it wasn't there. Since it was in an index you have two choices, try to rebuild the index or run a dbcc and fix the nature of the corruption in the index. since it is index 0 which should be the clustered index this could be leaf level corruption I would run the dbcc checkdb first to find out if there is any other corruption and fix it.

I hope that is a little better,

Wes

Johan Bijnens SSC Guru Points: 135376 More actions · Answer 4

euh ..

index 0 is the heap. (index 1 is the number for the clustered index, index 255 contains text, lob stuff)

before trying to mess with the details, use the system-delivered toolset diagnose and correct it

btw kl, my answer , even if not on top to the issue, provides a way of help. This Q has been posted 05/2004 , if (s)he would have to wait for this reply ....