Problem:

StarTeam 5.3SP1 : Server3

Resolution:

Patch #3 for StarTeam Server 5.3.192 and 5.3.214 (Service Pack 1)

Installation instructions

This patch should only be used if an upgrade from 4.2 SP3 to 5.3/5.3 SP1 was previously performed without first applying StarTeam Server 5.3 SP1 patch #2.

Shutdown the 5.3/5.3 SP1 StarTeam Server configurations and close the Server Tools application.
Backup the 5.3/5.3 SP1 StarTeam Server databases before running any of the following scripts.
Find the case below that fits your current situation and follow the instructions. Please be aware that if there are a lot of label overrides in your database that the scripts could take a few hours to complete.

MS SQL Server:

Case I: 4.2 SP3 data was not dropped after the upgrade was performed:
Open Query Analyzer
Point to the database
Copy/paste script starteam_sqlserver_fix_label_data.sql
Run it

Case II: 4.2 SP3 data is not available in the same database. You need to create a database called fix_42_data and restore the database backup of that was made just before the upgrade to 5.3/5.3 SP1.
Open Query Analyzer
Point to the database
Copy/paste script starteam_sqlserver_fix_label_data_in_different_db.sql
Run it

Oracle:

Case I: 4.2 SP3 data is not available in the same database. You need to selectively import serversettings and config_label_entry tables into your current production database schema user before following case II below.

Case II: 4.2 SP3 data was not dropped after the upgrade
Open SQL Worksheet
Connect to current production database
Copy/paste script starteam_oracle_fix_label_data.sql
Run it
Re-open the Server Tools and restart the 5.3/5.3 SP1 StarTeam Server configurations.

Description:

Resolves the problem of view label overrides not being upgraded properly when upgrading from 4.2 SP3 to 5.3/5.3 SP1. Label overrides are created whenever a view label is attached, detached or moved from one revision to another. This problem only exists when upgrading from 4.2 SP3 to 5.3/5.3 SP1.

Download :