Checked out element in the lost+found directory prevents a UCM Activity deliver

CM deliver operation fails due to an Activity that is checkedout but catalogued in the lost+found directory of the VOB.

Symptom An element version listed as CHECKEDOUT in the change set of a UCM activity points to lost+found and blocks the deliver from progressing. The other change set versions have been moved to a new activity and delivered. Running checkvob -hlinks and checkvob -ucm complete with no errors, but do not resolve the issue with the problem activity, and the checkout remains. Listing the properties of the activity show the change set version checked out to the lost+found directory: lost+found> cleartool lsact -long ACT00032163 activity "ACT00032163" 16-May-06.14:58:24 by Joe User (jou) "Created automatically as a result of 'Work On' action in ClearQuest" owner: jou group: liteline stream: jou-act3g-v1.0-2@/vobs/projects title: Draft of Test cases for UC01-1,2,3,7,8,10,11,30,32 and 04-2 change set versions: /vobs/act3g/lost+found/TC01-02SelectRang.8de766bce4e411da810d000183536e1d@@/main/jou-act3g-v1.0-2/CHECKEDOUT.21870 Listing the output of the lost+found directory show the element as checked out but removed: lost+found> cleartool ls ... TC01-02SelectRang.8de766bce4e411da810d000183536e1d@@/main/jou-act3g-v1.0-2/CHECKEDOUT from /main/jou-act3g-v1.0-2/0 [checkedout but removed] ... Attempts to list the file by name fails with the following error: lost+found> cleartool ls TC01-02SelectTimeRang.8de766bce4e411da810d000183536e1d cleartool: Error: Unable to access "TC01-02SelectTimeRang.8de766bce4e411da810d000183536e1d": No such file or directory. Attempting to remove the element from lost+found fails with an error: lost+found> cleartool rmelem -f TC01-02SelectTimeRang.8de766bce4e411da810d000183536e1d cleartool: Error: Pathname not found: "TC01-02SelectTimeRang.8de766bce4e411da810d000183536e1d".

Cause

The element is referenced in the change set of the UCM activity, but it is no longer present; hence checked out but removed. Attempts to cancel the checkout and remove the element from lost+found failed, which indicate that the checkout is in a corrupted state.

Resolving the problem

To remove the lost+found entry from the change set of the UCM activity, the view will need to be removed. Resolve all the checkouts in the view, aside from the one in lost+found, then remove the view and the entry will be removed from the change set of the UCM activity. Once the activity is empty, it can also be removed. Note: If the deliver is unable to process until the checkout is resolved (canceled) in the problem activity, then proceed with the deliver in a new view.

Selected activity deliver from stream "dev" to stream "int" is not supported

why attempts to deliver select activities from a child stream to the integration stream results in errors such as cleartool: Error: Selected activity deliver from stream "Bpr_MakefilesPatch_fdev" to stream "Bpr_LicensePatchM1_finteg" is not supported.

Symptom Attempts to deliver only selected activities within your development stream results in the following error: cleartool: Error: Selected activity deliver from stream "Bpr_MakefilesPatch_fdev" to stream "Bpr_LicensePatchM1_finteg" is not supported. cleartool: Error: Unable to deliver stream "Bpr_MakefilesPatch_fdev".

Cause

Imagine the hierarchy of streams as follows: Integration stream Group stream Development stream It is not possible to deliver from the group stream to the Integration stream, based on activities in the development stream. You are allowed to deliver from the development stream directly to the integration stream. The key to which activities may be delivered individually will depend on the order the activities were delivered to the group stream and which elements were modified in the activities. This follows the general rules for which activities may be delivered using selected activity deliver. Scenario: Suppose CQACT1 only modifies Component 1, and CQACT2 only modifies Component 2. Both activities are delivered to the group stream (it does not matter which order). Now suppose you want to deliver to the integration stream. If there are no dependencies between the activities either by elements or components, you may deliver CQACT1 or CQACT2 to the integration stream in any order using Alternate Target Deliver from the development stream. If there are dependencies between the activities, then delivering separate activities is not longer possible. For example, CQACT1 and CQACT2 modify the same element (CQACT1 modifies the first version while CQACT2 modifies the second version). CQACT1 is delivered first (selectively), CQACT2 is delivered second. At this point, attempts to deliver to the integration stream select activities changes. You can deliver CQACT1 selectively, but you cannot deliver CQACT2 selectively because the deliver baseline that was created when you delivered to the Group Stream includes CQACT1. CQACT2 now has a dependency with CQACT1. Note: The same logic applies even if you modify different elements in the same component because the second baseline created for the second deliver in the component is cumulative and includes the baseline created for the first deliver.

Resolving the problem

UCM does not currently provide for activity "independence". You need to deliver all required activities that are referenced as dependencies. Refer to technote 1303221 Knowledge Collection: UCM Activity Dependencies for a list of resources that provide further details about activity dependencies.