Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Error msg: Could not continue scan with NOLOCK due to data movement. Expand / Collapse
Author
Message
Posted Thursday, September 6, 2012 2:54 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, December 16, 2013 1:13 AM
Points: 24, Visits: 74
Hi, i keep getting the error msg;
msg 601:Could not continue scan with NOLOCK due to data movement when backing up my production database. My backup file destination is on a separate server(standby server remotely connected) were recovery is to take place on the backup file to keep the standby database in sync with my production database (this is a form of Log shipping).

Pls can anyone help me with error?

it is a backup job that runs the backup procedure

create procedure sp_bakdb

@dbname sysname ---name of the db to be backed up
@backuplocationpath nvarchar(256) ---unc path to location of the backed up database/log files; (linked server location)
@baktyp varchar (20) ---backup type (full or log)

as
declare @backupfilename = @backuplocationpath + '\' + <someformat>

set @dbname = lower@dbname
set @backuplocationpath = lower@backuplocationpath

---backup the database/log to the specified location
print 'Backing up ' + @dbname + ' to disk: ' + @backupfilename

if @baktyp = 'FULL'
backup database @dbname to disk=@backupfilename
else
begin
backup log @dbname to disk=@backupfilename
end
Post #1355129
Posted Thursday, September 6, 2012 11:42 AM
SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 8:28 AM
Points: 4,388, Visits: 9,508
You either have corruption in the database - or SAN issues causing problems.

First, run the following (when you can - not during business hours): DBCC CHECKDB ({your database}) WITH no_infomsgs, all_errormsgs;

If that reports errors, you will need to get those fixed as soon as possible.

If that does not report any errors, then you need to work with your storage team to see if there are errors on the SAN causing SQL Server to think the data has been moved.


Jeffrey Williams
Problems are opportunites brilliantly disguised as insurmountable obstacles.

How to post questions to get better answers faster
Managing Transaction Logs
Post #1355521
Posted Thursday, September 6, 2012 11:48 AM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Today @ 11:55 AM
Points: 23,034, Visits: 31,560
Are you still on version 8.00.197 of SQL Server 2000 or have you applied SP 4 yet?

This is a continuation of this thread:

http://www.sqlservercentral.com/Forums/Topic1354623-1550-1.aspx



Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
Post #1355528
Posted Thursday, September 6, 2012 12:00 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, December 16, 2013 1:13 AM
Points: 24, Visits: 74
Thanks for responding. I have ran chechdb and it report no issue. As for the san issue, will talk with the network team to look into that and will get back to you.

Pls if anyone else a respond pls post it up. And could anyone tell me how this could be related to vss?
Post #1355537
Posted Thursday, September 6, 2012 12:06 PM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Today @ 11:55 AM
Points: 23,034, Visits: 31,560
As you were told in the other thread, this issue may have been fixed in SP 2 or later for SQL Server 2000. In that thread you indicated that you were still using the RTM (or very close to it) version of SQL Server 2000. Have you applied the latest service pack?



Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
Post #1355543
Posted Thursday, September 6, 2012 12:14 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, December 16, 2013 1:13 AM
Points: 24, Visits: 74
About the sp4, I don't that yet but have sent for it and also my superior said that this error has occurred before and he can't remember being asked to provide sp4 to resolve the issue...but yeah
Post #1355549
Posted Thursday, May 29, 2014 4:40 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Sunday, June 8, 2014 3:02 PM
Points: 21, Visits: 52
Greetings!

I've landed in this post because I have a similar problem.

I work in an organization with several development servers. I have made linked servers to all of them from my notebook to keep some control of the changes made in every database on the servers and developed a process that goes through every server and database to track this information weekly.

Today everything went fine as always, except for one server: the error message was "Attempt to fetch logical page (1:110800) in database 14 failed. It belongs to allocation unit 14073963587174400 not to 281474978938880."

I connected to the instance (2008 R2) from the client in my notebook and effectively I couldn't see any element in that database, not even its properties. I executed DBCC CHECKDB but everything went OK. I tried to look at the error LOG but now the error is: "Could not continue scan with NOLOCK due to data movement" (shown in the window). This same error is shown when I try to query any other database from that instance through the linked server in my notebook. I have other instances in that server and they work fine.

Really, I've read all over and can't find an answer, these databases don't seem to be corrupt! thank you for your patience, I'll appreciate some answer.
Post #1575903
Posted Saturday, May 31, 2014 4:48 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, June 20, 2014 2:49 PM
Points: 10, Visits: 455
Are you still on SQL Server 2000??? This was a know issue in SQL Server 2000 - What causes this issue is if a row gets deleted by spid 1 while spid 2 is doing a scan with (either at READ UNCOMMITTED or WITH (NOLOCK)), then spid 2 face issue when it tries to read it. The row has to be deleted after spid 2 reads the index, but before it attempts to read the data row.

Microsoft released a fix for this issue: http://support.microsoft.com/kb/815008

Thanks..
Sanjiv Vinaik
Post #1576391
Posted Sunday, June 8, 2014 3:04 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Sunday, June 8, 2014 3:02 PM
Points: 21, Visits: 52
Thank you for your answer Sanjiv!

Anyway, it was a SQL Server 2008 R2, but I "fixed" the problem (notice the quotes) by restarting the instance. I've got no idea what might have caused this, but since I resstarted the instance it went fine again.
Post #1578686
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse