Deliver Cleartool Error Integration Activity Change Set Is Not Empty
not empty Integration activity change set is not empty; rebase -cancel; remove; undo; 1179696 Technote (troubleshooting) Problem(Abstract) This technote details some troubleshooting steps to assist support with resolving the rebase error, Integration activity change set is not empty, when using IBM Rational ClearCase UCM. Symptom Attempts to cancel a rebase operation results in the following error: P:\>cleartool rebase -cancel Rebase in progress unable to cancel delivery because another operation is trying to complete on stream "Test_Stream". Started by "Dev1" at 09/07/2000 01:05:00 PM. Are you sure you want to cancel this rebase? [no] clearcase unable to cancel delivery y Undoing checkins... Undoing file merges... Removing integration activity... cleartool: Error: Integration activity change set is not empty. cleartool: Error: Integration activity change set is not empty. cleartool: Error: Unable to cancel rebase. Cause This error is the result of: Removing versions from the change set of a rebase activity, or Removing the actual rebase activity while the rebase is still in progress Resolving the problem Use the below steps to help troubleshoot and resolve this error, which will allow the rebase to be canceled. 1. Run cleartool rebase -status to get the Integration activity name: P:\> cleartool rebase -status Rebase operation in progress on stream "stream:Test_Stream@\Project_VOB" Operation is currently being canceled - some data may already have been removed Started by "Dev1" on "07-Sep-00.13:05:00" Using integration activity " KRP200000783 ". Using view "Dev1_Test_Stream". Integration Stream Baselines: baseline:KRP2-ReqPro_INITIAL@\Project_VOB baseline:KRP_20000-07_Tdbb4_End@\Project_VOB Activities included in this operation: activity:KRP200000005@\Project_VOB activity:KRP200000042@\Project_VOB ..... 2. Run cleartool describe -long activity:activity_name to determine if the change set is actually empty: P:\> cleartool describe -long activity:KRP200000783@\Project_VOB activity "KRP200000783" created 07-Sep-00.13:05:02 by DEV1.CCUsers@H51044 "Integration activity created by rebase on 09/07/2000 01:05:00 PM. " master replica: BOSRAT@\Project_VOB owner: DOMAINA\Admin1 group: DOMAINA\CCUsers stream: Test_Stream@\Project_VOB title: rebase Test_Stream on 09/07/2000 01:05:00 PM. change set versions: clearquest record id: KRP200000783 Note: The change set is empty in the above output. 3. If there are versions listed under change set versions in the output of step #2, then remove the change set versions and try to c
"Dev_View" is not the view in which you started this operation cleartool: Error: Rebase in progress on stream; rebase; cancel; "does not match the view specified"; started; operation; reset; 1146614 Technote (troubleshooting) Problem(Abstract) This technote explains why canceling an IBM Rational ClearCase UCM rebase operation fails with the error, cleartool: Error: Rebase in progress on stream "Development_Stream" using view "Shared_Dev_View" does not match the view specified, and provides a solution to resolve the problem. Symptom Attempt to cancel a rebase operation fails with the http://www.ibm.com/support/docview.wss?uid=swg21179696 following error: # cleartool rebase -cancel -view Dev_View Rebase in progress on stream "Development_Stream". Started by "Joe_User" at 09/10/01 16:15:16. cleartool: Error: Rebase in progress on stream "Development_Stream" using view "Shared_Dev_View" does not match the view specified. cleartool: Error: View "Dev_View" is not the view in which you started this operation. cleartool: Error: Unable to cancel rebase. Cause The UCM views, Dev_View http://www.ibm.com/support/docview.wss?uid=swg21146614 and Shared_Dev_View, are attached to the same stream, Development_Stream. The rebase in this case was originally started in Shared_Dev_View, but the cancel operation is being attempted from Development_View. Generally, the views can be alternated for working on the stream, however, a rebase must be started and completed or canceled in the same view. Note: The above error will occur when the original view has been removed or for some reason cannot be accessed on the ClearCase network. Resolving the problem Where the Development view still exists and is accessible When possible, the rebase operation should be canceled from within the view that it was originally started from. Example: To resolve the above error, the rebase needs to be canceled from Shared_Dev_View: # cleartool rebase -cancel -view Shared_Dev_View Where the Development view is inaccessible There are instances where the original development view that was used to start the rebase is no longer available on the ClearCase network. The view may no longer exist, or it may still exist but it is not accessible. Note: In cases where the view still exists, but is not
Error: Cannot remove an activity with versions in its change set.; rmact; remove activity; change set; 1134544 Technote (FAQ) Question What is the required procedure for removing change set versions of http://www-01.ibm.com/support/docview.wss?uid=swg21134544 an IBM Rational ClearCase UCM activity in the command line interface? This technote steps through the required cleartool sub-commands for removing change set versions from a ClearCase UCM activity. Answer Important Considerations] The following procedure is used to remove checked in versions from the change set of a UCM activity using command line syntax. Note: For any checked out version listed in the change set, cancel the checkout and the version unable to will no longer appear in the change set list. Removing checked in versions should be done with discretion and under conditions that warrant such action. For example, instances where a deliver or rebase fails leaving checked in versions which are preventing the operation from being canceled as detailed in technote 1125189 and technote 1179696. When removing versions as a result of a failed rebase, then the checked in versions will be listed unable to cancel on the development stream, and vice-versa when removing versions as the result of a failed deliver operation (the checked in versions will be listed on the target stream). This is important because this procedure requires that the checked in versions be removed from a UCM stream. You need to know specifically what stream the change set versions are on to be sure and remove the correct ones. Note: Merge hyperlinks are removed from the source to the target version that was created as a result of a deliver or rebase operation; hence, there are no dangling hyperlinks left to cleanup, such as detailed in technote 1117462. File versions should be removed before removing the versions of directory elements. This will help avoid stranding any elements and causing them to get put into the lost+found; refer to technote 1120317 for more details. The following command is used to remove change set information: cleartool rmver -xbranch -xlabel -xattr -xhlink Refer to technote 1122442 for more details on this command and about removing interesting versions in UCM. [ Removing Checked In Versions Set into a UCM view attached to the stream that the activity is associated with and list of the available activities: M:\prj1_dev_vu2>cleartool lsact 02-Jun-06.14:59:50 rebase.prj1_dev.20060602.145948 administrator "rebase prj1_dev on 6/2/2006 2:59:48 PM." 08-Jun-06.08:58:29 test_activity