Error:
SQL Error 601. Could not continue scan with NOLOCK due to data movement.
SQL Sever Logs:
Message
Error: 605, Severity: 21, State: 3.
Message
Attempt to fetch logical page (13:2769683) in database 7 failed. It belongs to allocation unit 72057594291945472 not to 72057594369933312.
SELECT au.allocation_unit_id, OBJECT_NAME(p.object_id) AS table_name, fg.name AS filegroup_name,
au.type_desc AS allocation_type, au.data_pages, partition_number
FROM sys.allocation_units AS au
JOIN sys.partitions AS p ON au.container_id = p.partition_id
JOIN sys.filegroups AS fg ON fg.data_space_id = au.data_space_id
WHERE au.allocation_unit_id = 72057594291945472 OR au.allocation_unit_id = 72057594291945472
ORDER BY au.allocation_unit_id;
SELECT au.allocation_unit_id, OBJECT_NAME(p.object_id) AS table_name, fg.name AS filegroup_name,
au.type_desc AS allocation_type, au.data_pages, partition_number
FROM sys.allocation_units AS au
JOIN sys.partitions AS p ON au.container_id = p.partition_id
JOIN sys.filegroups AS fg ON fg.data_space_id = au.data_space_id
WHERE au.allocation_unit_id = 72057594369933312 OR au.allocation_unit_id = 72057594369933312
ORDER BY au.allocation_unit_id; Explanation
This error generally signifies page or allocation corruption in the specified database. SQL Server detects corruption when reading pages belonging to a table either by following the page linkages or by using the Index Allocation Map (IAM). All pages allocated to a table must belong to one of the allocation units associated with the table. If the allocation unit ID contained in the page header does not match an allocation unit ID associated with the table, this exception is raised. The first allocation unit ID listed in the error message is the ID present in the page header, and the second allocation unit value is the ID associated with the table.
Fix:
Restart SQL Server Services
Comments