Results 1 to 3 of 3
  1. #1
    Join Date
    Aug 2003
    Posts
    4

    Unanswered: 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

  2. #2
    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



    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

  3. #3
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    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.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •