DBCC CHECKDB error

  • Hi Experts,

    Please check this error:

    Msg 8928, Level 16, State 1, Line 1

    Object ID 2073058421, index ID 0, partition ID 72057594038321152, alloc unit ID 72057594042318848 (type In-row data): Page (1:143) could not be processed. See other errors for details.

    Msg 8939, Level 16, State 98, Line 1

    Table error: Object ID 2073058421, index ID 0, partition ID 72057594038321152, alloc unit ID 72057594042318848 (type In-row data), page (1:143). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.

    CHECKDB found 0 allocation errors and 2 consistency errors in table 'xxxxx' (object ID 2073058421).

    CHECKDB found 0 allocation errors and 2 consistency errors in database 'xxxxx'.

    repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (xxxxx).

    I don't have clean back up of this database.is it possible to get back my db with out any dataloss?

    Thank you,

  • No. Without a backup you're going to have to run CheckDB with repair_allow_data_loss to fix that. As the option implies it allows data loss and a single page from the mentioned table will be deallocated and any data on it will be lost. The page is in the heap, so it's the actual table.

    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
  • thank you for your help

  • Please consider it a lesson and backup your databases regularly. I should add verification of backups is equally important so verify your backups with proper restoration scenarios at regular interval as well.

Viewing 4 posts - 1 through 3 (of 3 total)

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