locked
split content database to new content database RRS feed

  • Question

  • I've got 8 site collections and 1 content database.  I have managed explicit paths for all the site collections.

    When I go run this command.

    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN>stsadm -o mergecontentdbs -url http://cesrvsp01/resources -sourcedatabasename WSS_Content -destinationdatabasename WSS_Content_RESOURCES -filename resources.xml -operation 3'

    I get this error

    http://cesrvsp01/resources
    Moving sites...
    Another site already exists at /resources. Delete this site before attempting to  create a new site with the same URL, choose a new URL, or create a new inclusion at the path you originally specified.

    I've got one web application, all I am trying to do is split the "resources" content to a new content db named WSS_Content_Resources

    Any idea why this doesn't work?

    Thanks

    Monday, November 17, 2008 5:37 PM

Answers

  •  

    Hello,

     

               After research, I’ve found that your issue is probably caused by you do not have the correct permissions to perform the operation.

                In order to move a site collection from one database to another, you must be a member of both the Farm Administrators group and the Local Administrators group, and must have the Full Control permission granted for any site collection that needs to be moved. To grant this permission, in Central Administration, click Application management, and then Application Security, and then Policy for Web application. The account that you use to perform this procedure must be a member of the db_owner fixed database role in SQL Server.

               After the site has been moved successfully, remove or change your account permission level by using the Policy for Web Application page. If your account is used for other services, reset it to the original permission level.

               If you do not have the correct permissions to perform the operation, you will receive the error message like you met.

              This is a KB article for you to take reference: http://support.microsoft.com/kb/939035/en-us

     

               Hope it can help you,

               Jerry


    Xing-Bing Yu
    Wednesday, November 19, 2008 7:49 AM