cleartool lsprivate=267

Explanation: A cleartool lsprivate=267 error is an error thrown by clearcase when it cannot connect to the clearcase vob.

Fix: Start the ClearCase view and mount the ClearCase vob. If neither of these fix the problem, check the conduit configuration for typos in the VOB name. Finally check the SCM configuration for typos in the view name

cleartool: Error: Unable to contact db server on host vob_server_name

Explanation: Gernerally this is a transient issue with the ClearCase vob server. There will most likely also be errors in the ClearCase administration logs, usually the mvfs log and the view log.

Fix: Allow the task to run again. If it continues to fail contact your ClearCase admin.

cleartool: Error: Activity not found: activity_name

Explanation: There are two possiblities for this error. First, the activity in question could have been deleted from the vob at some point during the SourceIQ ascquistion. Thus, we found the activity associated to a revision, but are no longer able to find the activity itself. The second possibilty is for SourceIQ systems that have recently been update to version 4.2.6. Prior to version 4.2.6 SourceIQ truncated activity names, thus if an activity was being used in a vob in which is was not created, the full activity name would be activity_name@\vob_name. But the SourceIQ server was not storing the @\vob_name portion.

Fix: Run the command: cleartool lsactivity activity_name in the clearcase view. This will tell you if the activity still exists. If the activity name does not include the @\vob_name portion, you need to run a cleartool describe on an element that is associated with the activity. The output of the describe command will give the full name of the activity. Once you have identified the full name of the activity or that the activity does not exist. Please contact support@sourceiq.com to get help in updating the SourceIQ database appropriately.