469,902 Members | 1,910 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,902 developers. It's quick & easy.

Could not find the index entry for RID...

Greetings. Today I was testing the sql backup/restore functions on our
primary server. I was able to backup my database without any problems
but when I tried to restore it, I received an error "Could not find the
index entry for RID '3610200101a03cc4b49d8bbc84bac50cbe042cecf76' in
index page (1:40), index ID 0, database 'walkthrough'." Thinking that
data had been corrupted somehow I tried another database and received a
similar error for that database. In the past, our service provider has
attempted to restore data to this server and the restore failed do to
another data corruption. The problem is, I can't find out where the
corruption is located or how to fix it.

When I open the restored database in enterprise manager, it returns the
above error and is unable to get a listing of my tables. In query
analyzer I am able to view my data but receive the index error when I
attempt to look at the information_schema data. When I try to run a DBCC
CHECKDB on the corrupted database it reports 0 errors and 0
inconsistencies.

So my diagnosis of the problem is that something is corrupting my system
tables and that problem shows up whenever I try to restore data from a
backup. There could be a hardware failure but I believe the failure
would affect more then just the sql system tables. Can anyone offer any
advice on how to find the corruption?

Thank you in advance

Richard Bailey

*** Sent via Developersdex http://www.developersdex.com ***
Jul 23 '05 #1
1 14382
Hi

If a DBCC CHECKDB does not help see
http://msdn.microsoft.com/library/de...err_1_23sk.asp
and
http://groups-beta.google.com/group/...b56fb232?hl=en
then you may want to call PSS. Also you may want to look for anything in the
event log and run some diagnostics on the disc.This will depend on what sort
of contract you have with the service provider.

http://msdn.microsoft.com/library/de...setup_1s8i.asp
http://support.microsoft.com/default.aspx

John

"Richard Bailey" <rb*****@401kexchange.com> wrote in message
news:I3****************@news.uswest.net...
Greetings. Today I was testing the sql backup/restore functions on our
primary server. I was able to backup my database without any problems
but when I tried to restore it, I received an error "Could not find the
index entry for RID '3610200101a03cc4b49d8bbc84bac50cbe042cecf76' in
index page (1:40), index ID 0, database 'walkthrough'." Thinking that
data had been corrupted somehow I tried another database and received a
similar error for that database. In the past, our service provider has
attempted to restore data to this server and the restore failed do to
another data corruption. The problem is, I can't find out where the
corruption is located or how to fix it.

When I open the restored database in enterprise manager, it returns the
above error and is unable to get a listing of my tables. In query
analyzer I am able to view my data but receive the index error when I
attempt to look at the information_schema data. When I try to run a DBCC
CHECKDB on the corrupted database it reports 0 errors and 0
inconsistencies.

So my diagnosis of the problem is that something is corrupting my system
tables and that problem shows up whenever I try to restore data from a
backup. There could be a hardware failure but I believe the failure
would affect more then just the sql system tables. Can anyone offer any
advice on how to find the corruption?

Thank you in advance

Richard Bailey

*** Sent via Developersdex http://www.developersdex.com ***

Jul 23 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by Tom | last post: by
1 post views Thread by Gustaf Liljegren | last post: by
reply views Thread by kris | last post: by
1 post views Thread by Waqarahmed | last post: by
reply views Thread by Salome Sato | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.