Post reply

I/O error (bad page ID) detected during read

  • November 11, 2005 at 10:35 am

    #110751

    Hello,

    We are getting following error when ever we are running a perticular stored procedure which is doing lots of order by and group by.

    Ran the DBCC Checkdb and it retured same errors.

    I have requested my system admin to look for any hardware related issues eventhough there is no error in event log.

    I already read the KB article 828339

    http://support.microsoft.com/default.aspx?scid=kb;en-us;828339

    2005-11-10 12:44:42.28 spid58    Error: 823, Severity: 24, State: 2

    2005-11-10 12:44:42.28 spid58    I/O error (bad page ID) detected during read at offset 0x00000044e42000 in file 'E:\sqldata\clrstest.mdf'..

    Any help is appreciated

    Thanks

    --

    Farhan


    FS

  • November 12, 2005 at 7:59 am

    #603545

    I would recommend to you reading the following article. Possible causes of your problems could be Lost Write and Stale Read conditions. This article explains how to detect them (usage of sqliostress utility, trace flag 818, forced flushing of buffer pages out of memory) and how to rectify the problem (disable caching etc.). It might help you. If none of these apply you will probably have to restore from last good backup or try to call MS.

    http://support.microsoft.com/kb/826433/

Viewing 2 posts - 1 through 1 (of 1 total)

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