SharePoint 2010 DB Migration – database is up to date, but some sites are not completely upgraded

I was migration several content databases to SharePoint 2010 using Powershell (Mount-SPContentDatabase command) and after the migration I went to Central Admin to check the databases status.

There I could see this message on one of the databases:
Database is up to date, but some sites are not completely upgraded.

Searching on Google for the solution I found several articles on using STSADM instead of the Powershell command. The article “SharePoint 2010 Content Database Migration, Re-Deploy Results in Foreign Key Constraint Error” is one of the examples I found with the STSADM recommendation. With further research, I also found some articles recommending to run the Upgrade-SPContentDatabase cmdlet to upgrade the content DB. The article SharePoint Upgrade has a good example of it and explains how to get the content DB GUID using the Get-SPContentDatabase cmdlet. I also tried this and even though the cmdlet returned sucessfully the database continued with the same status.

Finally, checking the Mount-SPContentDatabase Errors on 2nd and subsequent attempts of same database article I found the awesome recommendation on closing the Powershell window and open it again. I did it and finally I could run the migration successfully. The article didn’t explain why it happens but it says it is a known issue and happens after you leave the Powershell window open for a long time. I hope Microsoft works on solving this kind of issues because they can easily take a couple of days from our migration schedules.

See you,