brl8
asked on
MOSS 2007 upgrade fails: Could not continue scan with NOLOCK due to data movement
Hello All,
We are working on a SharePoint 2007 installation and attempting to upgrade it to SP2. The upgrade is failing with the following error: Exception: System.Data.SqlClient.SqlE xception: Could not continue scan with NOLOCK due to data movement
The consultant with whom I am working thinks this is a SQL Server error related to space issues on the Admin Content database.
When I look at sp_spaceused for this database I see the following:
size: 58 MB
Unallocated: 3.23 MB
reserved: 55696 KB
data: 43944 KB
index_size: 10504 KB
unused: 1248 KB
Since I don't know anything about space and how it is allocated and used in SQL Server, I wanted to know if this database has sufficient space, and if not, how would I go about giving it more space? Are we even on the right track?
Any suggestions or thoughts would be appreciated.
Thanks.
BRL
We are working on a SharePoint 2007 installation and attempting to upgrade it to SP2. The upgrade is failing with the following error: Exception: System.Data.SqlClient.SqlE
The consultant with whom I am working thinks this is a SQL Server error related to space issues on the Admin Content database.
When I look at sp_spaceused for this database I see the following:
size: 58 MB
Unallocated: 3.23 MB
reserved: 55696 KB
data: 43944 KB
index_size: 10504 KB
unused: 1248 KB
Since I don't know anything about space and how it is allocated and used in SQL Server, I wanted to know if this database has sufficient space, and if not, how would I go about giving it more space? Are we even on the right track?
Any suggestions or thoughts would be appreciated.
Thanks.
BRL
You will see this error if a database file is shrinking or it's data is moving to another file or another drive. If you are shrinking a file, stop the shrink operation during the upgrade.
This is not a space issue. It may be related to Updating Statistics on your databases, probably as an internal part of the upgrade process, or it may be related to restoring a corrupted database from a backup (again, probably as a part of the upgrade), or it could be from excessively fragmented, indexes, or it could be from several other causes, but it is not about space. You need to check the upgrade log and identify what is happening in the process at the time that the error is generated....
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks, bhess, I was thinking this was not a space issue.
Our plan of attack now is to do a fresh install of SharePoint on another server, connect the existing content database to it and then hopefully be good to go.
This is from upgrade.log - any thoughts?
[SPManager] [DEBUG] [10/2/2010 9:26:45 AM]: Upgrading [SPContentDatabase Name=SharePoint_AdminConte nt_5f894e0 9-7098-4e7 2-8d90-cd7 5f70a5322 Parent=SPDatabaseServiceIn stance].
[SPContentDatabaseSequence ] [DEBUG] [10/2/2010 9:26:45 AM]: Invalidating WYukon signature in SPContentDatabase Name=SharePoint_AdminConte nt_5f894e0 9-7098-4e7 2-8d90-cd7 5f70a5322 Parent=SPDatabaseServiceIn stance.
[SPContentDatabaseSequence ] [DEBUG] [10/2/2010 9:26:45 AM]: ---------------- Begin Table RowCount Dump ----------------
[SPSqlCommandFactory] [DEBUG] [10/2/2010 9:26:45 AM]: SqlCommand.CommandTimeout = 0
[SPSqlCommandFactory] [DEBUG] [10/2/2010 9:26:45 AM]: SqlCommand.CommandTimeout = 0
[SPContentDatabaseSequence ] [DEBUG] [10/2/2010 9:26:45 AM]: Table [dbo].[AllDocs] RowCount = 648
[SPSqlCommandFactory] [DEBUG] [10/2/2010 9:26:45 AM]: SqlCommand.CommandTimeout = 0
[SPContentDatabaseSequence ] [DEBUG] [10/2/2010 9:26:45 AM]: Table [dbo].[AllDocStreams] RowCount = 5534
[SPSqlCommandFactory] [DEBUG] [10/2/2010 9:26:45 AM]: SqlCommand.CommandTimeout = 0
[SPContentDatabaseSequence ] [DEBUG] [10/2/2010 9:26:45 AM]: Table [dbo].[AllDocVersions] RowCount = 0
[SPSqlCommandFactory] [DEBUG] [10/2/2010 9:26:45 AM]: SqlCommand.CommandTimeout = 0
[SPManager] [ERROR] [10/2/2010 9:26:47 AM]: Upgrade [SPContentDatabase Name=SharePoint_AdminConte nt_5f894e0 9-7098-4e7 2-8d90-cd7 5f70a5322 Parent=SPDatabaseServiceIn stance] failed.
[SPManager] [ERROR] [10/2/2010 9:26:47 AM]: Could not continue scan with NOLOCK due to data movement.
[SPManager] [ERROR] [10/2/2010 9:26:47 AM]: at System.Data.SqlClient.SqlC onnection. OnError(Sq lException exception, Boolean breakConnection)
....
[SPManager] [DEBUG] [10/2/2010 9:26:47 AM]: Elapsed time upgrading [SPContentDatabase Name=SharePoint_AdminConte nt_5f894e0 9-7098-4e7 2-8d90-cd7 5f70a5322 Parent=SPDatabaseServiceIn stance]: 00:00:01.
[SPManager] [INFO] [10/2/2010 9:26:47 AM]: Resetting the status of PersistedUpgradableObject: SPContentDatabase Name=SharePoint_AdminConte nt_5f894e0 9-7098-4e7 2-8d90-cd7 5f70a5322 Parent=SPDatabaseServiceIn stance to Online.
[SPManager] [DEBUG] [10/2/2010 9:26:47 AM]: Using cached [SPContentDatabase Name=SharePoint_AdminConte nt_5f894e0 9-7098-4e7 2-8d90-cd7 5f70a5322 Parent=SPDatabaseServiceIn stance] NeedsUpgrade value: True.
[SPManager] [ERROR] [10/2/2010 9:26:47 AM]: SPManager.Initialize failed.
[SPManager] [ERROR] [10/2/2010 9:26:47 AM]: Could not continue scan with NOLOCK due to data movement.
[SPManager] [ERROR] [10/2/2010 9:26:47 AM]: at System.Data.SqlClient.SqlC onnection. OnError(Sq lException exception, Boolean breakConnection)
Our plan of attack now is to do a fresh install of SharePoint on another server, connect the existing content database to it and then hopefully be good to go.
This is from upgrade.log - any thoughts?
[SPManager] [DEBUG] [10/2/2010 9:26:45 AM]: Upgrading [SPContentDatabase Name=SharePoint_AdminConte
[SPContentDatabaseSequence
[SPContentDatabaseSequence
[SPSqlCommandFactory] [DEBUG] [10/2/2010 9:26:45 AM]: SqlCommand.CommandTimeout = 0
[SPSqlCommandFactory] [DEBUG] [10/2/2010 9:26:45 AM]: SqlCommand.CommandTimeout = 0
[SPContentDatabaseSequence
[SPSqlCommandFactory] [DEBUG] [10/2/2010 9:26:45 AM]: SqlCommand.CommandTimeout = 0
[SPContentDatabaseSequence
[SPSqlCommandFactory] [DEBUG] [10/2/2010 9:26:45 AM]: SqlCommand.CommandTimeout = 0
[SPContentDatabaseSequence
[SPSqlCommandFactory] [DEBUG] [10/2/2010 9:26:45 AM]: SqlCommand.CommandTimeout = 0
[SPManager] [ERROR] [10/2/2010 9:26:47 AM]: Upgrade [SPContentDatabase Name=SharePoint_AdminConte
[SPManager] [ERROR] [10/2/2010 9:26:47 AM]: Could not continue scan with NOLOCK due to data movement.
[SPManager] [ERROR] [10/2/2010 9:26:47 AM]: at System.Data.SqlClient.SqlC
....
[SPManager] [DEBUG] [10/2/2010 9:26:47 AM]: Elapsed time upgrading [SPContentDatabase Name=SharePoint_AdminConte
[SPManager] [INFO] [10/2/2010 9:26:47 AM]: Resetting the status of PersistedUpgradableObject:
[SPManager] [DEBUG] [10/2/2010 9:26:47 AM]: Using cached [SPContentDatabase Name=SharePoint_AdminConte
[SPManager] [ERROR] [10/2/2010 9:26:47 AM]: SPManager.Initialize failed.
[SPManager] [ERROR] [10/2/2010 9:26:47 AM]: Could not continue scan with NOLOCK due to data movement.
[SPManager] [ERROR] [10/2/2010 9:26:47 AM]: at System.Data.SqlClient.SqlC
ASKER
thanks!