Results 1 to 7 of 7
  1. #1
    Join Date
    Dec 2015
    Posts
    1

    Unanswered: I get the following error messages when an application submits a query:

    Msg 605, Level 21, State 3, Line 1
    Attempt to fetch logical page (1:224) in database 11 failed. It belongs to allocation unit 72058253744865280 not to 72057594040287232


    What’s wrong?

  2. #2
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    Possible database corruption.

    Run the following on your database.
    Code:
    dbcc checkdb() with no_infomsgs
    This will tell you what if anything is corrupt in the physical structure of the database.

  3. #3
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    You have a corrupted database. You need to start by restoring the most recent intact backup:

    1. Find your most recent error-free DBCC check
    2. Get the most recent backup that came before the clean DBCC
    3. Restore that backup to another database name (be certain that you move the files when you restore).
    4. If necessary, manually recover the data that you can from your corrupt database into the restored image.
    5. Rename the corrupted database with a scratch name
    6. Rename the restored/manually recovered database with the production name.

    At this point, you'll have a working, usable database image.

    -PatP
    In theory, theory and practice are identical. In practice, theory and practice are unrelated.

  4. #4
    Join Date
    Dec 2015
    Posts
    1

    database

    If DBCC CHECKDB or CHECKTABLE reports an error (which should be Msg 2533), then the page is damaged or an incorrect page. You should restore from a backup to resolve the problem. If you cannot restore from a backup, use the repair options with DBCC CHECKDB. To find the cause of this problem you should use techniques as you would with other database corruption errors including:
    Check for hardware or system level problems (A tool such as SQLIOSIM can be helpful to do this. SQLIOSIM ships with SQL Server 2008 and SQL Server 2008 R2 and does not require a separate download)
    Ensure you have the PAGE_VERIFY=CHECKSUM database option turned on. While it is possible to still encounter a Msg 605 error with checksum enabled (Ex. "scribbler" problem or incorrect page provided from I/O system), enabling checksum can provide definitive proof that the page was modified incorrectly within the I/O system.
    Try to restore a database backup you know that will be "clean" (no errors from CHECKDB) and transaction log backups you know span the time when the error was encountered. If you can "replay" this problem by restoring a "clean" database backup and transaction logs then contact Microsoft Technical Support for assistance.
    For more information about database corruption problems see here: https://www.fixtoolbox.com/sqlserverfix.html

  5. #5
    Join Date
    Dec 2015
    Posts
    2

  6. #6
    Join Date
    Dec 2015
    Posts
    2

  7. #7
    Join Date
    Jan 2016
    Posts
    24
    Provided Answers: 1
    This error occurs when Microsoft SQL Server detects database corruption.

    To fix this error
    >First try to drop the tables involved in the error message and recreate those tables from scratch.
    OR
    >Extract all the data out into a new database.
    OR
    >Use DBCC PAGE to try to figure out which tables in the database are affected and drop their statistics.
    OR
    >Use third party SQL Server MDF Recovery to repair corrupt database

Posting Permissions

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