domingo, 14 de febrero de 2010

MOSS 2007 SP2 & Orphan items

Share it Please

One of the improvements included on the Service Pack 2 for MOSS 2007 to make our life more easy is the way to eliminate orphan items in our Content database.

Now, we have to follow these steps to clean up our database:

Run the following stsadm command

Stsadm –o enumallwebs –databasename <Content db name> -databaseserver <db server name>

It should show a result similar to that:

<Sites Count="1">

  <Site Id="14f9385d-f543" OwnerLogin="domain\angelp" InSiteMap="False">

    <Webs Count="10">

      <Web Id="f5355528-6b02" Url="/" LanguageId="1033" TemplateName="STS#0" TemplateId="1" />

      <Web Id="86d9b8e3-2287" Url="/Test" LanguageId="1033" TemplateName="STS#1" TemplateId="1" />

      <Web Id="0d855bfe-b0ea" Url="/ClientD" LanguageId="1033" TemplateName="STS#1" TemplateId="1" />

      <Web Id="1cb190f0-c8d1" Url="/Financials" LanguageId="1033" TemplateName="STS#1" TemplateId="1" />

      <Web Id="c127df5a-865e" Url="/Toolkit" LanguageId="1033" TemplateName="STS#1" TemplateId="1" />

      <Web Id="90281063-6224" Url="/Management" LanguageId="1033" TemplateName="STS#1" TemplateId="1" />

      <Web Id="e84bcd49-1b5d" Url="/Client" LanguageId="1033" TemplateName="STS#1" TemplateId="1" />

      <Web Id="12d77124-a53f" Url="/Reporting" LanguageId="1033" TemplateName="STS#1" TemplateId="1" />

      <Web Id="d764935a-7d90" Url="/Container" LanguageId="1033" TemplateName="STS#1" TemplateId="1" />

      <Web Id="cbd1e30d-69ef" Url="/Testing" LanguageId="1033" TemplateName="STS#1" TemplateId="1" />

    </Webs>

  </Site>

</Sites>

And then you have to run the deletesite command for all webs where InSiteMap is equal to False:

Stsadm –o deletesite –force –siteid < site id> -databaseserver <db server name> -databasename <Content db name>

On the above example:

Stsadm –o deletesite –force –siteid 14f9385d-f543 –databaseserver myServer –databasename myDB_Content

And anymore steps are needed. However, It seems that enumallwebs command output only locates Content db orphans, not Config db orphans. Which is OK, because Content db orphans are more common and much more difficult to delete. In order to eliminate the Config db orphans, you still need to detach/attach the content db as I explained on “MOSS 2007 and Orphan objects – Part II” post.

No hay comentarios:

Publicar un comentario

Project Mgmt. Professional

Project Mgmt. Professional

AWS Architect

AWS Architect

ITIL Fundamentals

ITIL Fundamentals