Fixing projects that contain linked and unlinked activities

After you enable a project to work with HCL Compass, some of the project activities can remain unlinked to HCL Compass records. Similarly, when you disable the link between a project and an HCL Compass user database, some activities may remain linked. The following scenarios can cause your project to be in this inconsistent state:

• A network failure or a general system crash occurs during the enabling or disabling operation and interrupts the activity migration.
• The HCL Compass user database can become corrupted, forcing you to restore a backed-up version of the user database. That version of the user database is out of sync with the PVOB that contains the project that is linked to the user database.
• You use the cleartool command-line interface to rename an activity or a project. When you rename an activity or project from the command-line interface, the UCM integration with HCL Compass does not update the corresponding user database record with the name change. As a result, the HCL VersionVault and HCL Compass objects are not synchronized.
• The project VOB is in an HCL VersionVault MultiSite configuration, and unlinked activities were added by an HCL VersionVault MultiSite synchronization operation to the local PVOB project, which is enabled to work with HCL Compass.