I would like to finish these series about Orphan objects in MOSS 2007 talking about two considerations that could be very important that you keep in mind when you are “fighting” with orphan objects and your farm is in one of the cases described below.
Considerations if you are working with a mySite farm
If you are working with a mySite farm or any other farm with a big number of top level sites where you can find hundred of orphan objects, it is better that you execute the following steps to clean it:
- Clean old sync info
- Detach Content DB
- Execute the upgrade on the farm
- Attach Content DB
Considerations if the Infrastructure Update is not installed on your farm
If your farm has not been upgraded to the Infrastructure Update you have to take into account to execute the following command before to detach the Content DB:
Stsadm –o preparetomove –contentdb <myContentDB> -site <mysiteURL>
This is very important because if you didn’t run this command the Content db would be assigned a new GUI when reattached.
To check if the IU is installed on your farm, from Central Administration site go to Operations > Servers in Farm. In this page you will see the Database Schema Version in the top of the screen and a list of servers with the version numbers listed in the relevant column against each server in the farm.
You can also see the database schema version in Site Settings, Modify All Site Settings in the Site Information section. Or you can look the MOSS configuration database (SQL Server) of your site collection and open the Versions table, there will be entries in this table with the versions that have been applied to in your farm and the date when the Service Pack, hot fix or Rollup was applied.
The version corresponding for the IU upgrade is 12.0.0.6318, if your farm is in this version or above you don’t need to execute the Preparetomove command and you can forget about this consideration section.
No hay comentarios:
Publicar un comentario