Corrupt database

  • I have a SQL 2000 database which is read by a MS Access application. The SQL

    Database is updated by a DTS package run by a SQL Job. The Job is the only

    thing that updates the database. This has run fine for several years without

    a problem.

    For the second time in the last few months the database has turned up as

    corrupt, returning the errors noted below (thank God for good backups). Since

    the programming has not changed, my thought is that there are hardware

    problems. Can I get some options as to what the problem may be?

    Other Information:

    SQL Server Standard Edition (sql server 2000)

    Version 8.00.2039 (SP4)

    Access returned the following error:

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

    Doing a "DBCC CHECKDB WITH ALL_ERRORMSGS, NO_INFOMSGS;" returns the following:

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 1977058079, index ID 0: Page (1:117) could not be processed. See

    other errors for details.

    Server: Msg 8939, Level 16, State 1, Line 1

    Table error: Object ID 1977058079, index ID 0, page (1:117). Test (IS_ON

    (BUF_IOERR, bp->bstat) &&

    bp->berrcode) failed. Values are 2057 and -1.

    Server: Msg 8976, Level 16, State 1, Line 1

    Table error: Object ID 1977058079, index ID 1. Page (1:117) was not seen in

    the scan although its parent

    (1:5884) and previous (1:116) refer to it. Check any previous errors.

    Server: Msg 8978, Level 16, State 1, Line 1

    Table error: Object ID 1977058079, index ID 1. Page (1:118) is missing a

    reference from previous page

    (1:117). Possible chain linkage problem.

    CHECKDB found 0 allocation errors and 4 consistency errors in table

    'Aplus_EmpOrgPayHistory' (object ID

    1977058079).

    CHECKDB found 0 allocation errors and 4 consistency errors in database

    'CustomDB'.

    repair_allow_data_loss is the minimum repair level for the errors found by

    DBCC CHECKDB (CustomDB ).

  • Please don't cross post. It just wastes peoples time and fragments replies.

    No replies to this thread please. Direct replies to: http://www.sqlservercentral.com/Forums/Topic685614-265-1.aspx

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

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