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 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?
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 be checked out: sometimes a right issue can prevent the unco, sometimes, the version was already checked in.
Now, if the activity associated with the rebase is actually empty, there is an utilty called 'ucmutil' which can reset the rebase state, making it "vanish".
But that should be used with caution, and under the supervision of IBM Rational Support.
See "Canceling UCM rebase fails with error: cleartool: Error: Rebase in progress on stream" and "About ucmutil".
Related
When I am trying to check in a file in ClearCase, I receive an error:
cleartool> ci -nc 1234.txt
cleartool: Error: Branch not consistent with stream attached to current view.
cleartool: Error: Unable to check in "1234.txt".
Does anyone know what's causing this? It started happening this morning.
So far, I have synchronized the stream and the view with no luck. Please help.
If so, what activity? - tied to a CC activity that is associated to an old stream, CQ activity is tied correctly
That means it is an UCM project with CQ integration.
When I look under version tree of this element, the element checkout is under a branch that is different from the stream the checkout was initiated from??? How can that happen?
That can only happen if the view used for the checkout had a different config spec than the one generated from the UCM stream. It is best to undo that checkout, and start again in the proper view.
Well, all I can do is add questions:
How old is the checkout?
Is it on a NON-UCM branch?
If so, when was the component added to the stream's configuration?
If you describe the version, is it associated with an activity? If so, what activity?
Has anything else "odd" happened to the view of late? (restored view from backup, etc.?)
What you're probably going to need to do is do a ct unco -keep. This will undo the checkout and make the view look at the version selected by the current stream configuration. Then
Set an activity
Check out the file again
Verify that the version created is on the current stream's branch
Copy the .keep file to the checked out file
Check it in.
As I see it, just create another new view on required Stream and copy the file into it.
When I am trying to do Undo Checkout through my ClearCase GUI, its showing me a error message as "Error Undoing the CheckOut for "E:\Views\Stream Name\File Name'.
Lock on Versioned Object base "\ prevents operation uncheckout
Unable to cancel Checkout for 'E:\Views\Stream Name\File Name' "
Please suggest me how can i solve this issue
You need to make sure what is locked.
If it is the UCM project for instance, you need to run (or to ask your ClearCase admin to run) a cleartool unlock:
cleartool unlock project:projectname#\pvobname
If this is a file/folder, it is possible it is locked by another user, in which case it can be unlocked at any time, allowing you to proceed.
Adding to VonC's response - it's possible that the vob itself was locked for some reason. Why would a vob overall be locked? If it was being backed up, for example. Someone may have run a "cleartool lock vob:myvob" or similar for some reason. Then ran "cleartool unlock vob:myvob" afterwards. I'd ask your clearcase admin for an explanation.
we are using snapshot view (UCM).
While we tried to add source control a folder it fails with following error.
Rational ClearCase Explorer
---------------------------
Error adding 'D:\cc_view\IS-Dev1\Impl\Install\ViewDeployment' to source control.
Checkout is currently disabled for element "D:\cc_view\IS-Dev1\Impl\Install". An update appears to have been aborted or errors were encountered during an update. An update must be performed on the element to enable a checkout. Checkout is currently disabled for element "D:\cc_view\IS-Dev1\Impl\Install". Its config spec rule information is currently unavailable due to either an aborted update or an update in progress.
We have updated the view once again and stop and start the clearcase related services.
But still no improvement. When we look at properties of view-> advanced tab . it show Load state: Update cancelled.
I think this state may play a role. How to solve this and allow it to add to source code control?
You need to make sure to launch the update at the root directory of the snapshot view (above the vobs), because UCM might complain because of the configuration change.
If the Stream has been rebased, then an update would ask for you to accept the new configuration and launch a full update, but only if done from the root directory of the view.
Check also the logs of those updates (file *.updt in the root folder of the view), any error in it would mean a "Update cancelled" for the view.
A way to get a full update in your case would be (still at the root folder, as in this technote -- for CCRC but also valid for a full ClearCase installation):
cleartool setcs -current
Previous update or checkout is uncompleted. You have to update your snapshot view. You can run
cleartool setcs -current
OR
ClearCase Explorer->(on left panel--snapshot_name) right click-> Update View->Yes
that operation take a long time. That operation completed after this problem fixed.
Warning: Dont stop updating processing. You shouldn't start this operation while starting. Because you cant do progress while clear case updating to view.
We are working in multisite UCM environment.
In while my colleague was trying to rebase stream and he was prevented from doing it as there was already a delivery was pending in that stream.
Now in his view that rebase activity is set by default.
After the delivery is accepted in master replica, some one else has rebased the same stream.
Now my colleague is not allowed to rebase as the stream is update. But while we were trying to change the default activity from view properties , it doesn't allow and saying that rebase in progress.
Will it automatically corrected after synchronizaztion? or it will be keep on occuring , why it occurs and how to solve it?
If you are dealing with snapshot view, the first thing to do is a full update (from the root directory of the view)
You also need to check the rebase status of the Stream you are (and on the right site depending on where the rebase was actually started, in order to take into account the multisite aspect).
cleartool rebase -status -stream yourStream#\YourPVob
As long as that status says a rebase is in progress, it needs to be completed (especially if it was in its "complete" phase: cancelling a rebase can fail for a variety of reason: see technote 2059393).
That status will mention the name of the view currently affected by said rebase.
When I try to 'rebase' my stream in clear case, I get the 2 options : 'Resume rebase' and 'Undo rebase'.
But both of them give me errors. It seems a previous rebase failed and left the stream in a corrupted state.
How to solve this?
I tried stopping and starting ClearCase but no luck.
EDIT: the error is :
IDispatch error #14083
Execution of a hook failed during the action Complete. It was the ACTION_COMMIT hook attached to the UCMUtilityActivity "CR00155721".
The reason for the failure was:
Trouble communicating with VOB database: "\Alerts_Proj".
Check database log on VOB host "123yyyyy.com".
Could not perform requested operation: a UCM/ClearQuest data
inconsistency may exist:
ClearQuest "UCMUtilityActivity" record "CR00155721" is linked to a UCM object
that can not be found.
Unable to complete the rebase activity in ClearQuest.
Unable to undo set of integration activity.
Unable to complete integration.
FYI I've also seen this happen when the "CQIntSvr11.exe" fails. It seems to occur when you need to use the application on the same machine with different users (e.g. admin and developer account).
If you kill the process using task manager and then retry the operation the IDispatch 14083 should stop and then you can use your stream again.
One solution might be deactivating the trigger, but this could be put by the ClearCase-ClearQuest link and not be possible without severing completely that link.
So you can start by checking out this IBM technote with your ClearCase administrator:
This error occurs because the UCM project VOB and associated activities have been removed, ClearQuest is still looking for this information and needs this information to remove the defect.
This issue is the result the ClearCase items being removed before the ClearQuest defects and project.
Solution
To resolve this issue perform the following to fix the Activity so it can be deleted:
Browse to the ClearCase utils directory:
c:\program files\rational\clearcase\etc\utils
Run the following command from a command prompt:
Note: This command cannot be performed in the GUI
squid_patch <DBNAME> -activity ucm_vob_object ""
Note: It will display an advisory message, but it will change the field in ClearQuest.
Delete the ClearQuest record.
Remove the UCM project with the following command:
squid_patch <DBNAME> -project ucm_vob_object ""