Thursday, January 24, 2013

Error 605 Attempt To Fetch Logical Page In Database 2 - Tempdb

Error 605 Attempt To Fetch Logical Page In database 2 - Tempdb.

ERROR:
Error : 605, Severity: 21, State: 3.    Attempt to fetch logical page (4:566920) in database 2 failed. It belongs to allocation unit 5692560307852607488 not to 3819061315151921152.

Workaround

As per the error message we can find out that the database 2 failed, it means the issue with only tempdb database. This error usually occurs when we use "NOLOCK" locking hint on queries or "read-uncommitted" isolation level.

There are couple of options to resolve this issue.

Option 1:  Run a DBCC CHECKDB on error giving database, If minimal repair required then run the DBCC with ALLOW_DATA_LOSS.


Option 2:  In some scenario stopping and restarting SQL Server eliminates this error. When you stop and restart the sql server always the new tempdb create so in this scenario it will resolved the issue, if the issue with any user database? check my next article.


Option 3: Add a clustered index to the temp table. Using the example below, create the table as follows:

Create Table #t (pk INT IDENTITY(1,1) CONSTRAINT PK_pk PRIMARY KEY CLUSTERED, f int )
sql server 2008 attempt to fetch logical page in database 2 failed. attempt to fetch logical page in database 2 failed. attempt to fetch logical page in database 7 failed. an attempt was made to fetch logical page. attempt to fetch logical page that belongs to different object. attempt to fetch logical page in database 5 failed. Attempt to fetch logical page. in sql server 2012. in sql server 2008 R2. in sql server 2005. In sql server 2000. Attempt to fetch logical page (1:15) in database 'X' belongs to, DBCC CheckDB show no errors but I get Error 605 when doing, Data corruption cause - attempt to fetch logical page, Attempt to fetch logical page in database 'DBName' belongs to object 'TableName', not to object 'TableName'. Error: 605, Severity: 21,

0 comments:

Post a Comment