Professional Web Applications Themes

I/O error (torn page) detected during read at offset - Microsoft SQL / MS SQL Server

Hi, Environment: SQL Server 2000 + SP3, Windows 2000 +SP3 I am running a storedprocedure through Java and got the following error: [Microsoft][ODBC SQL Server Driver][SQL Server]I/O error (torn page) detected during read at offset 0x000000254ea000 in file 'd:\Program Files\Microsoft SQL Server\MSSQL\data\ServiceDB_Data.mdf'. Can some body help me in solving this problem. Also I found one of the table which is being accessed by the above storedprocedure, is not giving back any results, when I make direct query in the Query yzer (e.g. Select * from Table123 where 1 =2 ) and the query is running for ever. Thanks, -- RS ...

  1. #1

    Default I/O error (torn page) detected during read at offset

    Hi,

    Environment: SQL Server 2000 + SP3, Windows 2000 +SP3

    I am running a storedprocedure through Java and got the following error:

    [Microsoft][ODBC SQL Server Driver][SQL Server]I/O error (torn page)
    detected during read at offset 0x000000254ea000 in file 'd:\Program
    Files\Microsoft SQL Server\MSSQL\data\ServiceDB_Data.mdf'.

    Can some body help me in solving this problem. Also I found one of the table
    which is being accessed by the above storedprocedure, is not giving back any
    results, when I make direct query in the Query yzer (e.g. Select * from
    Table123 where 1 =2 ) and the query is running for ever.

    Thanks,
    --
    RS
    Please Respond to News Group Only


    RS Guest

  2. #2

    Default Re: I/O error (torn page) detected during read at offset

    Ram,

    Torn page detection occurs due to incomplete I/O operations by reasons
    beyond user control such as power failures,outages etc.Usually, this error
    is momentary and if not, it indicates database corruption.Ask your system
    admin to check for disk corruption.From your part, make sure to run DBCC
    CHECKDB or DBCC CHECKTABLE on that culprit table.

    --
    Dinesh.
    SQL Server FAQ at
    http://www.tkdinesh.com

    "RS" <hr.lucent.com> wrote in message
    news:%phx.gbl... 
    table 
    any 
    from 


    Dinesh.T.K Guest

  3. #3

    Default Re: I/O error (torn page) detected during read at offset

    Thanks for the reply. I ran DBCC CHECKTABLE and got the following result:

    --------------
    Server: Msg 8928, Level 16, State 1, Line 1
    Object ID 517576882, index ID 0: Page (1:76405) could not be processed. See
    other errors for details.
    Server: Msg 8939, Level 16, State 1, Line 1
    Table error: Object ID 517576882, index ID 0, page (1:76405). Test (IS_ON
    (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
    DBCC results for 'ServiceTbl'.
    There are 324116 rows in 228159 pages for object 'ServiceTbl'.
    CHECKTABLE found 0 allocation errors and 2 consistency errors in table
    'ServiceTbl' (object ID 517576882).
    repair_allow_data_loss is the minimum repair level for the errors found by
    DBCC CHECKTABLE (ServiceDB.dbo.ServiceTbl ).
    ----------------

    by checking the result we can notice that there are some consistency errors.
    What should I do to correct this problem.

    Thanks in advance.

    RS

    "Dinesh.T.K" <mail.tkdinesh.com> wrote in message
    news:phx.gbl... 
    > table 
    > any 
    > from 
    >
    >[/ref]


    RS Guest

  4. #4

    Default Re: I/O error (torn page) detected during read at offset

    Ram,

    As indicated by the output and as suspected earlier, this is because of
    database corruption.Your best bet would be to restore from a valid and
    latest database backup.You can ofcourse run DBCC CHECKTABLE
    ....REPAIR_ALLOW_DATA_LOSS but unless you know what you are doing, this can
    be risky.

    --
    Dinesh.
    SQL Server FAQ at
    http://www.tkdinesh.com

    "RS" <hr.lucent.com> wrote in message
    news:OU%phx.gbl... 
    See 
    errors. [/ref]
    error [/ref]
    system [/ref][/ref]
    error: 
    > > table [/ref][/ref]
    back 
    > > from 
    > >
    > >[/ref]
    >
    >[/ref]


    Dinesh.T.K Guest

Similar Threads

  1. Mac/Firefox Shockwave 3D offset error
    By fhgljhkhlhlkjlh in forum Macromedia Director 3D
    Replies: 2
    Last Post: December 13th, 08:21 PM
  2. InDesign is shutting down. A serious error was detected.
    By Cindy_Pearce@adobeforums.com in forum Adobe Indesign Macintosh
    Replies: 2
    Last Post: July 6th, 07:57 PM
  3. #25512 [Bgs]: preg_replace Offset error
    By koni at 2complex dot net in forum PHP Development
    Replies: 1
    Last Post: September 12th, 02:17 PM
  4. #25512 [NEW]: preg_replace Offset error
    By koni at 2complex dot net in forum PHP Development
    Replies: 0
    Last Post: September 12th, 11:16 AM
  5. Full recovery and torn page detection
    By martin in forum Microsoft SQL / MS SQL Server
    Replies: 0
    Last Post: July 16th, 07:39 AM

Bookmarks

Posting Permissions

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

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139