DBCC CHECKDB with Msg 8921, Msg 824

  • Paul Randal

    One Orange Chip

    Points: 29438

    You might be able to try the hack-copy described at https://www.sqlskills.com/blogs/paul/disaster-recovery-101-fixing-a-broken-boot-page/ but for page 1:58 instead of 1:9. No idea if it will work as I've never tried it, but it's worth a try. Pleasxe od it on a copy of the corrupt database. Thanks.

    Paul Randal
    CEO, SQLskills.com: Check out SQLskills online training!
    Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
    SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
    Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005

  • jaganeee

    SSC Veteran

    Points: 263

    Paul Randal - Wednesday, November 1, 2017 1:39 AM

    You might be able to try the hack-copy described at https://www.sqlskills.com/blogs/paul/disaster-recovery-101-fixing-a-broken-boot-page/ but for page 1:58 instead of 1:9. No idea if it will work as I've never tried it, but it's worth a try. Pleasxe od it on a copy of the corrupt database. Thanks.

    Compared the Prev Backup and Corrupted Mdf  file using hex editor.
    half of the 1:58 page data is not identical to backup mdf. 
    58 of the hex location is 0x74000. 
    i check before and after page hex data to some extend. 
    it is identical.
    so i replaced the hex data from backup to corrupted mdf file from 0x74000 to 0x76000
    saved the file and attached the modified file to the sql server 2005.
    now it works like a charm.
    thanks for this idea and couple of days worry came to an end.
    really learned a lot in this 2 days.

  • Paul Randal

    One Orange Chip

    Points: 29438

    Excellent!

    Paul Randal
    CEO, SQLskills.com: Check out SQLskills online training!
    Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
    SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
    Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005

  • jaganeee

    SSC Veteran

    Points: 263

    Update on the Steps :

    After attaching the Recovered DB.
    I Queried
    DBCC Checkdb  show no error and i can able to open all the tables.

    I Generated the script with Schema and Data and saved it.
    Then i tried to insert some rows but it shows Primary Key Error.
    When i Checked Design of the Table and Data there is nothing wrong with anyone.
    I thought the Recovered DB from the Corrupted DB is not Working 100% fine.

    So I Recreated the Database from the Scratch.
    Retrieved the Schema from the working Db that i backed up on Jan 10.
    and Retrieved all the table Data from the Script that i already saved.
    Now it is working flawlessly.

    Thanks for all who are supporting me to recover the data.

  • Johnson Welch

    SSCoach

    Points: 18748

    Here are the step by step process to troubleshoot SQL Server error 8921:
    https://www.systoolsgroup.com/updates/troubleshoot-sql-server-error-8921-error-8967/

Viewing 5 posts - 16 through 20 (of 20 total)

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