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
This error Msg 605 is faced by the user when they try to login with any user that is not Sys admin type user. This error Msg comes in red color the user are able of this type of error incorruption of pages (s) when they try to login with SA, Administrator or other SysAdmin login, then the error did not come in red color.
When the severity Level is 21, the user session is disconnected and then the error is written into the SQL error log and Windows Application Event Log as Event ID 605. The severity could also be 12 that only results in the error returned to the client application. In the error msg, the allocation unit is an ID that recognizes which index and object page belongs to. Know here what causes the error msg 605:
Causes of the Error Msg 605:
Due to severity 21.
This problem could be a problem with the database page or else with the SQL Server engine while determining the estimated allocation unit should be.
The severity is 12
The severity of this error can also be Level 12 if the query fails as it is using read uncommitted isolation level or the NOLOCK query hint which is also called Dirty Read
Solution to fix the error:
In severity 21
If the DBCC CHECKDB or CHECKTABLE shows an error which is Msg 2533, then the page might be damaged or incorrect page. And it should be recovered from the backup to fix the issue but if you are unable to recover from a backup then you need to repair it with DBCC CHECKDB. So to find out the cause of the problem make use of the given technique as you might do with other database corruption errors:
Firstly check for hardware or the system level problems
Make sure that the PAGE_VERIFY=CHECKSUM database option is turned on. Although you can even get the error Msg 605 after enabling the checksum, allowing checksum can give definitive proof that the page was modified incorrectly within the I/O system.
In severity 12 follow given points:
- Do not read uncommitted isolation level (or NOLOCK hint)
- Prepared for retrying the query till the error was not faced by you
- Do not make changes to the affected table (s) during running the query.
So if the DBCC CHECKDB does not fix the error and you are facing the problem continuously then make use of the professional third party repair tool to fix the error.
Solution to Fix Error Msg 605:
SQL Repair Tool is the most trustworthy tool to fix error in SQL Server Database files. It also recovers corrupted and damaged database files without backup. It also recovers views, indexes, tables, stored procedures, unique/primary keys etc. that are saved in your damaged SQL database
Steps to solve the error:
Step 1: Stop running MS SQL server, the repair process is done on the copy of corrupt database so tap to ‘OK’ button and continue.
Step 2: Now click on the ‘Select database’ button and select the path of corrupt MDF file. After that search for your corrupt database file by using ‘Look in’ and ‘File Type’ button. To start with the repairing process click on the ‘Scan file’ button.
Step 3: The complete listing of recoverable objects of a database is in the tree view on the left side of the window. Tapping to the object, you can see the preview.
Step 4: Click on the ‘Start Repair’ icon to begin the process. To save the repaired file in the desired location click on the browse button and assign the path, otherwise the repaired file will be saved in the ‘Default SQL Location’. Click on the ‘Ok’ button.
Conclusion- Hope with the given solution you can fix the error msg 605 in the SQL Server. It can be repaired easily with the SQL Repair tool it is the best solution to fix any error in the SQL server database files. It is easy to use and recovers the data easily without any hassle.