Upgrading mainline branches

Mainline branches created in Surround SCM 2008 or earlier must be upgraded to RDBMS format in Surround SCM 2009 or later. Mainline branches that require upgrading before they can be used are appended with 'non-RDBMS database'. Keep the following in mind.

A database cannot include two mainline branches with the same name. If the destination database already includes a mainline with the same name as the mainline you are upgrading, you must select a different destination database.

During the upgrade, Surround SCM attempts to match users and security groups in the mainline branch to users and groups on the Surround SCM Server. If matching names are found, Surround SCM assumes they are the same user or group. If users in the mainline do not exist on the server, they are created without assigned licenses. If security groups in the mainline do not exist on the server, they are created without any security commands enabled. Surround SCM also tries to match Helix ALM connection information.

If you are upgrading a mainline branch from Surround SCM 5.x or earlier, you are prompted to automatically upgrade the branch to Surround SCM 2008 format before it is upgraded to RDBMS format.

After mainline branches are upgraded, you must manually upgrade labels. See Upgrading legacy labels.

Note: Back up the mainline branch directory before you upgrade it.

1. In the Surround SCM Client, select the mainline branch you want to upgrade and choose Tools > Administration > Upgrade Mainline Branch.

2. Click Yes when you are prompted to upgrade the mainline branch.

3. Select the Destination database for the upgraded mainline branch and click OK.

Note: Only select the Ignore errors during upgrade option if you have already used the Surround SCM Analyze Utility and were unable to repair issues causing errors.

The upgrade information is sent to the Surround SCM Server for validation.

If the validation succeeds, the upgrade starts and the Upgrade Status dialog box opens.

If the destination database does not include any Surround SCM tables, you are prompted to create them.

If the validation fails, the Test Connection dialog box opens with error information. You can copy and paste the text into an email or text file and email it to your DBA for help.

Note: The old database is not deleted from the original location during the upgrade. You may want to manually delete the directory after verifying the branch is successfully upgraded to RDBMS format.