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 ""
Related
I am getting below error while updating the view.
Problems were encountered while retrieving view synchronization and data.
Clearcase CM server error: Unable to access "vob name" : unknown error in vob
Clearcase CM server error: Error 2 config spec load rule problems encountered
How to troubleshoot that error message?
You need to access the logs (both locally or on the server) to know more.
It used to be cleartool getlog (ClearCase 7.x, even for CC 8.x)
cleartool: Error: Checkout is currently disabled for element "element_name".
Its config spec rule information is currently unavailable due to either an aborted update or an update in progress
That is similar to an older CC (7.0.x) described in this technote:
Possible cause for symptom 1:
If an update, rebase or deliver operation is not currently in progress for the view in question, the error can often be attributed to the view being out of sync with the stream.
Try:
cd /path/to/snapshot/view
cleartool setcs -stream
Possible cause for symptom 2:
Hijacked nocheckout means that the version hijacked in the view is no longer the version the config spec selects from the VOB.
Rename the hijacked file and update the view.
Check out the version from which the file was hijacked.
Copy the hijacked file over the checked-out version.
Merge from the current version to the checked-out version.
The version can now be checked in.
Possible cause for symptom 3:
Per the error message explanation noted above, the problem may be caused by an issue with the view's config spec or an aborted or incomplete view update.
Try:
cd /path/to/snapshot/view
cleartool setcs -current
(original answer)
It can be a right issue, as illustrated by this thread.
Check group permissions on user and on those two VOBs.
Do you rely on the CLEARCASE_PRIMARY_GROUP environment variable?
If so, check the value of the user performing the update.
Compare the rights of the vob with the ones for your current snapshot view that you are trying to update:
cd /path/to/snapshot/view
cleartool lsview -l -full -pro -cview
If the CLEARCASE_PRIMARY_GROUP is not set properly, it is easier to:
set it to the right group (ie the primary group of the vob, or one of the secondary groups)
delete and recreate your view.
(if you do not want to delete/recreate your view, you can fix_prot 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 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".
I am getting following
Rational ClearCase Explorer
---------------------------
Error checking out 'C:\Projects\TestServlet.java'.
Lock on activity "activity_test_name" prevents operation "change activity".
Unable to check out "C:\Projects\TestServlet.java".
The correct procedure to allow you to checkout that file would be to include you in the list of users exempted on that lock: see cleartool lock man page.
But you need to be the owner of the pvob in which the activity or the current Stream has been declared, or root (or privileged user on Windows).
If the activity only is locked, another way would be for you to create another activity.
cleartool mkact anotherActivity
and try your checkout then. It should have unset the current (locked) activity, and set a new one.
But if the Stream itself is locked (or even the vob/pvob), then you need to ask your ClearCase admin for an unlock.
See for instance IBM technote "Lock on activity prevents operation change activity", which illustrate how that "activity locked" error message is, in this case, misleading.
But that was for CC2003, and I suppose you are using a more recent version of ClearCase.
Someone with administrative control over the VOB you're using has locked the activity so that you cannot make a check-out. Speak to the people in charge to find out why.
The problem is (most probably) not that you don't have permission in general to do it. And you get a different error if the VOB is locked for backup.