Fatal error 824

  • Im using sql2005 and in a simple query in the mngt studio return the error:

    Msg 21, Level 24, State 1, Line 1

    Warning: Fatal error 824 occurred at May 16 2007 11:07AM. Note the error and time, and contact your system administrator.

    Someone know what is this error and how to fix it ?

    Thanks

     

  • You got trouble in River City. According to MS:

    The 824 error indicates that a logical consistency error was detected during a read. A logical consistency error is a clear indication of actual damage and frequently indicates data corruption caused by a faulty I/O subsystem component.

     

    Time to get kicking with DBCC. I hope you've been testing your backups on a regular basis.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • I have seen it before.

    Right click on My Computer icon, select manage, Open the Event Viewer Tree, Select Application and check there for the time of the error to see what happened to your system. If nothing there then do the same on the SQL Server Machine is connected remotely.

     

  • - hacer new query en master.

    - alter database dbname set emergency

    - ALTER DATABASE DBname SET SINGLE_USER WITH ROLLBACK IMMEDIATE

    - dbcc checkdb ('dbname', repair_allow_data_loss)

    - alter database dbname set multi_user

    saludos

  • mobile (11/18/2008)


    - hacer new query en master.

    - alter database dbname set emergency

    - ALTER DATABASE DBname SET SINGLE_USER WITH ROLLBACK IMMEDIATE

    - dbcc checkdb ('dbname', repair_allow_data_loss)

    - alter database dbname set multi_user

    saludos

    If you decide to repair_ALLOW_DATA_LOSS be warned that you may not like the results.

    My advice is to check first if the problem is in NC indexes pages which you can drop/recreate

    If that is not the case you should try to use backups to get the data back.

    If you just don't care about the data then doing as posted above may be OK.

    In any instance check your hardware !!!


    * Noel

  • mobile (11/18/2008)


    - hacer new query en master.

    - alter database dbname set emergency

    - ALTER DATABASE DBname SET SINGLE_USER WITH ROLLBACK IMMEDIATE

    - dbcc checkdb ('dbname', repair_allow_data_loss)

    - alter database dbname set multi_user

    saludos

    Repair should NOT be a first thing tried. As the name implies, it looses data. Not maybe. Not perhaps. It will cause data loss.

    Please run the following and post the results

    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
  • Find out what is causing the error, then do a dbcc checktable, odds are an index is out of whack, rebuild indexes on that table.

  • Considering that this thread is almost 3 years old, I'm guessing the OP has come right somehow.

    Rebuilding indexes is not a way to fix corruption. It might (read might) make the problem disappear, but that's because rebuilding an index deallocates pages. If the damaged page is deallocated, the error appears to go away, but it wasn't fixed.

    Take a look at this article. http://www.sqlservercentral.com/articles/65804/

    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
  • Nice article Gail.Thks.

    Regards,
    Saravanan

  • Thank you very much to all for your contribution.

    During these years, the server has been changed and the sql server has been migrated to 2008.

  • Found this thread and link to Gail's article today during my search for answers to address a "Fatal Error 824". Waiting on the db check to complete so I know what direction to go next.

  • If you need specific advice, please start a new thread in the appropriate forum (based on SQL version) and post the output of the CheckDB.

    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 12 posts - 1 through 11 (of 11 total)

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