Cleartool Error Unable To Cancel Rebase
Contents |
is removed cleartool: Error: Unable to find view by uuid; cleartool: Error: Unable to cleartool rebase command get view handle; unknown; deliver; uuid; removed view; cancel; resume; continue; clearcase rebase stop; kill; failed; target; integration; 1194392 Technote (troubleshooting) Problem(Abstract) This technote details a deliver error that clearcase rebase to latest baseline can occur if the target view becomes unavailable (or removed) while a deliver is still in progress when using IBM Rational ClearCase UCM. Symptom Attempts to complete
Clearcase Rebase To Older Baseline
or resume a deliver, result in the following error: C:\ClearCase_storage\project_snapshot_devint>cleartool deliver -complete cleartool: Error: Unable to find view by uuid:4bb6c357.3e794e15.8c29.d4:9e:2f:19:6e:2e, last known at "unknown:unknown". cleartool: Error: Unable to get view handle. cleartool: Error: Unable to recreate target view context. cleartool: Error: Unable to restore operation. cleartool: Error: Unable to restore from pvar. cleartool: Error: Unable rebase stream in clearcase to deliver stream "project5235_devint". Cause The target view that was associated with the deliver when it was started is no longer available, which left the deliver operation in an unresolved state that it cannot process or terminate. If you need to know more details about the deliver operation that is in-progress, such as who initiated it, then use the command "cleartool deliver -status" Diagnosing the problem To determine which view is unavailable, review the error to see which stream has the issue. Resolving the problem Try to recover the target view Try using a new target view If the above are unsuccessful, contact IBM Rational Client Support Try to recover the target view If you are able to determine why the view is no longer available, attempt to resolve the problem with the view and proceed with the deliver. For example, if the view was mistakenly unregistered or untagged in the region: Register and or tag the view in the region: cleartool mkt
set to rebase activity Fixes are available Rational ClearCase Fix Pack (7.1.2.5) for version 7.1.2 Rational ClearCase Fix Pack (8.0.0.1) for version 8.0 unable to cancel delivery because another operation is trying to complete Rational ClearCase Fix Pack (7.1.1.8) for version 7.1.1 Rational ClearCase Fix Pack
Unable To Cancel Rebase Because Another Operation Is Trying To Complete.
14 (7.1.2.14) for 7.1.2 Rational ClearCase Fix Pack 11 (8.0.0.11) for 8.0 Rational ClearCase Fix Pack 12 (8.0.0.12) for
Clearcase "unable To Cancel Delivery"
8.0 Rational ClearCase Fix Pack 15 (7.1.2.15) for 7.1.2 Rational ClearCase Fix Pack 13 (8.0.0.13) for 8.0 Rational ClearCase Fix Pack 16 (7.1.2.16) for 7.1.2 Rational ClearCase Fix Pack 17 http://www-01.ibm.com/support/docview.wss?uid=swg21194392 (7.1.2.17) for 7.1.2 Rational ClearCase Fix Pack 14 (8.0.0.14) for 8.0 Rational ClearCase Fix Pack 18 (7.1.2.18) for 7.1.2 Rational ClearCase Fix Pack 15 (8.0.0.15) for 8.0 Rational ClearCase Fix Pack 19 (7.1.2.19) for 7.1.2 Rational ClearCase Fix Pack 16 (8.0.0.16) for 8.0 Rational ClearCase Fix Pack 17 (8.0.0.17) for 8.0 Rational ClearCase Fix Pack 18 (8.0.0.18) for 8.0 Rational ClearCase http://www.ibm.com/support/docview.wss?uid=swg1PM33853 Fix Pack 19 (8.0.0.19) for 8.0 Subscribe You can track all active APARs for this component. APAR status Closed as program error. Error description In IBM Rational ClearCase, if a rebase is canceled ( by example via the command 'cleartool rebase -cancel -force') from a different view than the view it was started in and the views do not share a region, then the rebase is canceled, but the result is: 1) the rebase activity is not deleted 2) the original view is still set to this activity. This can happen when a user would cancel a rebase from a Windows view after starting the rebase from a Unix view. As example, from the command line the following output is generated by 'cleartool rebase -cancel -force' cleartool: Error: Unable to find view by uuid:xxxxxxxxxx, last known at 'unknown:unknown'. cleartool: Error: Unable to get view handle. cleartool: Warning: Unable to construct object 'xxxxxxxxxx'. Rebase in progress on stream 'd'. Started by '?username?' at 2/28/2011 1:33:14 PM. Undoing checkins... Undoing file merges... Removing integration activity... cleartool: Error: Activity 'activity:rebase.d.20110228.133314@\t1_test' is set in view '?no-tag-i
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings http://stackoverflow.com/questions/12143425/unable-to-undo-rebase-stream and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; unable to it only takes a minute: Sign up Unable to undo rebase stream up vote 1 down vote favorite We were trying to rebase our stream. After click on complete we got issue like some thing is corrupted. [Sorry my collegue did not take the screenshot of error] we tried to redo the rebase operation. It said unable to collect information unable to cancel about view When we try undo rebase we got following error. Rebase Stream --------------------------- Error cancelling rebase of stream 'IELoc--Dev100'. Integration activity change set is not empty. --------------------------- OK --------------------------- How to complete or undo the rebase now? clearcase clearcase-ucm share|improve this question edited Aug 27 '12 at 14:00 asked Aug 27 '12 at 13:55 Samselvaprabu 3,5841466137 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote accepted If you are in the process of cancelling, there is no going back: you must proceed all the way to completion of that "cancel" operation. The technote "Rebase fails with error: integration activity change set is not empty" can give some elements to resolve the situation. The problem can occur when other external operations have been done during the rebase: a cleartool rmver (delete version), for instance, would be very dangerous. The idea of a cancel (of a deliver or a rebase) is to undo checkout all the versions previously checked out in order to be merged. You need to make sure all those versions can