SQL Server

  • Error 823: i/O ERROR (BAD PAGE ID) DETECTED DURING READ AT OFFSET 0x00000017d300000 in file 'C:\DATABASE\ADD_DATA.MDF'

    It's urgent

    can anyone help me ?

    Thanks in advance

  • 823 is an IO error. It means that SQL asked for a page and the OS returned an error. It's a very serious condition and could indicate that you have hardware problems.

    Do you know when the error started?

    Do you have a known good backup?

    Please run the following and post the output

    DBCC CheckDB(' < Database name >') WITH NO_INFOMSGS

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Thanks

    I have already tried this one, but my database is not attached so that it can't execute

  • Did you detach the database?

    Can you reattach it?

    Do you have a good backup?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Thanks for reply

    The database is already detached and i don't have its backup

  • You can try reattaching the database. Depending on the corruption it might succeed.

    Why no backup?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • "Why no backup? "

    Here is a good one - I got paged at 1AM last night for a inaccessable SQL Server. I had never heard of the server before and had no access rights, so advised the client that I would not be able to assist but they could escallate to my management. This is an out-sourcing and the contract clearly states what servers are supported.

    Management agreed the DBAs would perform a best effort to assist at triple time rates.

    The system database are on one drive and were fine but the user databases were on a different drive that had failed. The last database backup was run in 2004.

    Turns out that the "server" was actually a workstation under someone's desk and the business had done all of the installation without IT assistance.

    Great fun !

    SQL = Scarcely Qualifies as a Language

  • Have Backup but the data of backup is approx. 1 month old

    thanks

  • Can you reattach the database?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Yes Backup i can attach

  • Not the backup.

    You said the database had being detached. Can you reattach the database files to the SQL instance?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • No i can't attach the database , i can restore the database backup

  • What error do you get from attaching? If you can't attach the DB, then you're only real option is to restore the backup you have and live with the data loss.

    And once you have the DB back, make sure that you set up a good backup plan so that this doesn't happen again.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Hello,

    I have the same problem of Msg 823 I/O error (bad page ID) but

    for the system database tempdb.mdf

    I have already checked the size of tempdb.mdf which is not full, and I moved the tempdb.mdf to another location in the disk, but the problem remains.

    Any ideas?

    thanks in advance!

  • Can you run a checkDB on model?

    Does a restart of SQL fix the problem?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 15 posts - 1 through 14 (of 14 total)

You must be logged in to reply to this topic. Login to reply