Workaround: Synchronizing base ClearCase MultiSite replicated VOBs with Rational Team Concert

Paul Komar
Last Updated: July 27, 2012
Build Basis: Rational Team Concert 4.0

Summary

If you are synchronizing a branch type in a replicated VOB using the Rational ClearCase Synchronizer, do not use branch mastership because the synchronizer might not synchronize the versions on the remotely mastered branches. Specifically, do not use the “-master” option when using the “mkelem” cleartool command or its equivalents in the Rational ClearCase graphical user interfaces. Also, do not change the mastership of a branch using the “chmaster” cleartool command or its equivalents in the Rational ClearCase graphical user interfaces.

More Information

The Rational ClearCase Synchronizer for branch types (known as the base ClearCase Synchronizer) tracks the versions that have been synchronized with the Jazz Team Server by recording the synchronization time. Versions newer than that time are imported into the Jazz Team Server on the subsequent synchronization. For versions created on a remotely mastered branch, their creation times are recorded at the remote site, but the versions might not be visible at the site where the Rational ClearCase Synchronizer runs. As a result, those versions might be missed by the synchronization attempt. Because their creation dates are before the recorded synchronization time, they are not synchronized into the Jazz Team Server.

Related Information

The following link points to related information:

• Using the Rational ClearCase Synchronizer and Importer: Guidelines for Rational ClearCase users