Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.

Welcome, Guest
Guest Settings

Thread: SQl

Permlink Replies: 1 - Last Post: Mar 29, 2016 8:14 AM Last Post By: Arnaud Lavigne Threads: [ Previous | Next ]
flacaruedas fla...

Posts: 1
Registered: 4/23/16
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 23, 2016 4:59 AM
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?
Arnaud Lavigne

Posts: 1
Registered: 4/29/16
Re: SQl
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 29, 2016 8:12 AM   in response to: flacaruedas fla... in response to: flacaruedas fla...
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: SQL Server Fix Toolbox

Edited by: Arnaud Lavigne on Mar 29, 2016 8:12 AM
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02