Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Error

Author  Topic 

ssrikrish
Yak Posting Veteran

69 Posts

Posted - 2005-08-23 : 14:17:02
This error message was thrown in a SQL server 7.0 database. Please let me know the cause and fix.

I/O error (bad page ID) detected during read of BUF pointer = 0x14682100, page ptr = 0x64ac8000, pageid = (0x1:0x33b0), dbid = 51, status = 0x801, file = E:\xxx\abcd.mdf

eyechart
Master Smack Fu Yak Hacker

3575 Posts

Posted - 2005-08-23 : 14:34:46
sounds like corruption to me. Have you run DBCC CHECKDB on your database?

Might be worthwhile to re-post this in the Data Corruption Issues forum here. http://www.sqlteam.com/forums/forum.asp?FORUM_ID=22

Run the DBCC CHECKDB and paste the results in a new post in that forum. Don't use any of the options to try and fix the data yet, just get the report.


-ec
Go to Top of Page

eyechart
Master Smack Fu Yak Hacker

3575 Posts

Posted - 2005-08-23 : 14:36:09
or just change the title of you original post to 'SQL 7 Data Corruption' or something similar.


-ec
Go to Top of Page

ssrikrish
Yak Posting Veteran

69 Posts

Posted - 2005-08-23 : 20:49:57
I ran CHECKDB as soon as I received the error. No corruption errors.
Go to Top of Page

eyechart
Master Smack Fu Yak Hacker

3575 Posts

Posted - 2005-08-23 : 21:19:54
do you have any disk errors in your system event log?



-ec
Go to Top of Page

ssrikrish
Yak Posting Veteran

69 Posts

Posted - 2005-08-27 : 09:43:06
Thanks for the input guys. Apparently, the disk had bad blocks. We have replaced the disks. Things are running smoothly after that. I believe it will save some sleepless nights for me. It seems like hardware life is a key on any db server.
-- sri
Go to Top of Page

eyechart
Master Smack Fu Yak Hacker

3575 Posts

Posted - 2005-08-27 : 13:23:45
quote:
Originally posted by ssrikrish

Thanks for the input guys. Apparently, the disk had bad blocks. We have replaced the disks. Things are running smoothly after that. I believe it will save some sleepless nights for me. It seems like hardware life is a key on any db server.
-- sri




Thanks for letting us know how you resolved the issue.


-ec
Go to Top of Page
   

- Advertisement -