If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > Microsoft SQL Server > I/O error (bad page ID) detected during read at offset 0x0000000f3e4000

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 08-25-03, 05:11
Bluetooth Bluetooth is offline
Registered User
 
Join Date: Aug 2003
Posts: 4
I/O error (bad page ID) detected during read at offset 0x0000000f3e4000

Hi,

Can anyone help me with this error?

Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC SQL Server Driver][SQL Server]I/O error (bad page ID) detected during read at offset 0x0000000f3e4000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\RVHS_database.mdf'.

What should i do to recover my database? Please help me out
Reply With Quote
  #2 (permalink)  
Old 08-25-03, 08:36
dbadelphes dbadelphes is offline
Registered User
 
Join Date: Feb 2003
Location: Montreal, Canada
Posts: 117
Re: I/O error (bad page ID) detected during read at offset 0x0000000f3e4000

use DBCC CHECKDB (use NOINDEX first; id an index is corrrupted it won't be a problem), then try REPAIR_FAST or REPAIR_REBUILD (it's time consuming) - see Books Online for more



Quote:
Originally posted by Bluetooth
Hi,

Can anyone help me with this error?

Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC SQL Server Driver][SQL Server]I/O error (bad page ID) detected during read at offset 0x0000000f3e4000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\RVHS_database.mdf'.

What should i do to recover my database? Please help me out
__________________
Steve
Reply With Quote
  #3 (permalink)  
Old 08-25-03, 10:31
rdjabarov rdjabarov is offline
Registered User
 
Join Date: Jul 2003
Location: San Antonio, TX
Posts: 3,611
ooops, I don't think the recommended switches will do the trick. It
's REPAIR_ALLOW_DATA_LOSS that will fix page allocation errors (which is what you have here). Do it within a transaction and don't commit untill you see what repairs are done and what errors got fixed.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On