StarTeam 5.3SP1 : Server17

0 Likes

Problem:

StarTeam 5.3SP1 : Server17

Resolution:

Patch #17 for 5.3.214 (Service Pack 1) for StarTeam Server
Build 5.3.214.17 (Service Pack 1)

Installation instruction

This patch requires that StarTeam Server 5.3.192 or 5.3.214 (Service Pack 1) be installed first. This patch does not include the new documentation that was released with 5.3.214 (Service Pack 1). It is very important that you consult the new documentation that was included with 5.3.214 (Service Pack 1) for the changes included with that release. The complete 5.3.214 (Service Pack 1) can be downloaded from the www.borland.com website or CDs may be requested.

  1. Shutdown the 5.3/5.3 SP1 StarTeam Server and close the Server Tools application if they are running 5.3 server configurations.
  2. Backup the database and repository.
  3. Install Server17.exe, it will prompt you for the location of your installation folder. Change the location if necessary.
  4. Re-open the Server Tools as desired and run the upgrade on any 4.2 SP3 server configurations as desired or restart 5.3 server configurations.
  5. A problem was introduced in some 5.2 SP1 patches and 5.3 SP1. Contact Borland Technical Support to determine if the bad_label_excp.sql script should be run to determine if there are any labels that may need to be manually fixed to resolve this problem. To fix these labels, each folder needs to be reattached to the problematic label. If folders are known to have been detached and then reattached then those should be the only ones that need to be reattached. If a label is reattached to a child folder, its parent folders will be reattached to the label. If a file is reattached to a label, its parent folders will be reattached. The script should be rerun to ensure that the labels have been fixed properly.
  6. If resolving the UTF8 problem, the UTF8 Converter utility will need to be re-run against a restored database to resolve the issue this patch addresses. See the Note below for important customization information.

Description:

  1. Resolves a situation where StarTeam Clients would hang when trying to connect to a StarTeam Server.

    The following is also included in patch #13

  2. Resolves a problem that occurred after a Purge was stopped in the middle of the operation. Subsequent purges would hang.

    The following is also included in patch #12

  3. Resolves a StarTeam Server intermittent crash when attaching labels to multiple items at one time. Problem was introduced in patch #11.
  4. Resolves a StarTeam Server crash due to an intermittent timing issue generating StarTeamMPX event message.
  5. Resolves promotion state database anomalies gracefully.
  6. Resolves an issue with migrated custom text fields receiving an incorrect column size.
  7. Resolves ?START WITH cannot be less than MINVALUE at "ST.CREATE_Label", line 1? error when copying labels.
  8. Resolves UTF8 Converter utility problem where text fields were overwritten for Oracle configurations when the option "Update all table applying codepage" was used.

    Note: The UTF8 Converter does not convert custom field information. You may have non-ASCII characters used as custom field display names or as the names of enumerated values. For example, you might be using the Euro character as the name of an enumerated value. After the upgrade, non-ASCII characters may be missing from names or entire names may be blank. You must correct these names yourself.

    If you are upgrading from 4.2 SP3, you may run the old 4.2 SP3 server configuration at the same time as the upgraded 5.3 configuration. Open two StarTeam clients and copy the custom field display names and custom enumerated values from 4.2 SP3 to 5.3. Selecting item_type->Advanced->Custom from the menu bar displays the Customize dialog. This dialog lists fields that can be customized. Double-clicking a field (or selecting a field and clicking Edit) displays the Modify Field dialog. The Modify Field dialog displays the internal name (which must be ASCII) and the display name (which needs to be examined). If the field is an enumerated field, the Modify Field dialog also displays the names of the enumerated values (which also need to be examined).

    If you are upgrading from 5.1, you might like to take screen shots of the Modify Field dialog for each custom field that will be affected. Selecting item_type->Advanced->Custom from the menu bar displays the Customize dialog. This dialog lists fields that can be customized. Double-clicking a field (or selecting a field and clicking Edit) displays the Modify Field dialog. The Modify Field dialog displays the internal name (which must be ASCII) and the display name (which needs to be examined). If the field is an enumerated field, the Modify Field dialog also displays the names of the enumerated values (which also need to be examined). You might want to resize this dialog before taking the screen shot.

    If you have already upgraded from 5.1, run both servers (5.1 would have to be run from a backup copy). Then you can compare the contents of the Modify Field dialogs for each custom field in each release, and make any needed changes.

    The following is also included in patch #11

  9. Resolves an issue where a file shared multiple times could not be attached to a revision label.
  10. Resolves an ?Invalid enumerated field upgrade? error when upgrading from 4.3 SP3 to 5.3 SP1. The upgrade must be re-performed after the patch is applied.

    The following is also included in patch #7

  11. Resolves a random byte exception.

    The following is also included in patch #6

  12. Resolves a View Compare/Merge problem when merging a parent and child file without merge tracking enabled made changes to the parent file appear as deletions.

    The following is also included in patch #4

  13. Resolves a problem with view labels where items attached to a label are shown correctly in ?current? view but are missing when the view is rolled back to the labeled configuration. This problem occurs when folders are detached and later attached to a view label.

    The following is also included in patch #2

  14. 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. It will not resolve this issue after an upgrade has been run. If an upgrade cannot be rerun from the beginning, then this patch will not resolve the problem. Request patch #3 if that is the case. It contains scripts that can be run to resolve the problem after the fact.



Download :

Old KB# 28424
Comment List
Related
Recommended