September 24, 2004 at 1:07 pm
these started appearing in the sql log
Could not retrieve row from page by RID because the requested RID has a higher number than the last RID on the page. Rid pageid is (1:43266) and row num is 0x8c.Page pointer = 0x319d6000, PageId = (1:43266), status = 0x8, objectid = 1614628795, indexid = 0, DBID 9..
Have no idea why or what to do
ANyone ever seen this
September 25, 2004 at 9:45 am
ouch. I've never seen this, but I'll tell you what I'd be doing if I did.
I'd run DBCC CHECKDB to see if I had any errors. While that was running, I'd be on Microsoft Knowledge Base website, searching for that type error to see if there was a reported bug in my version of SQL.
If both those failed, I'd take a look at my indexes on the table that is unhappy (you probably can figure that out by using the objectid and indexid (which I believe the error states is 0?) 1 means it's a Clustered Index, and >1 means it's a nonclustered index. So, I'm not sure, but 0 might mean there isn't an index and the table is a heap. Find out how many indexes you have on that table, if any. If you have a Clustered Index, rebuild it. If you only have non-clustered Indexes or no indexes at all, then create a clustered index on as unique a column as possible that already exists in the table. Once this is down, you can drop the Clustered Index, run UPDATEUSAGE (because you just dropped a main index), and see if that clears up the errors. If you have the pleasure of adding a column to the table, then I'd suggest adding a Identity Column to the table and make it a permanent Clustered Index.
...sorry for the incorrect plural usage of the word Index, but I just hate Indices. Sounds so whimpy.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply