I tried to update a clear case view with CCRC tool. Sometimes the view will be locked if last update was aborted for some reason, and couldn't be updated before the lock is broke. Is there anyone could help to tell me how could I unlock this view with CCRC tool?
Here's the error message when i run command update in rcleartool.
CRMAP7009: CCRC command "Update" failed: Error:
"com.ibm.rational.clearcase.remote_core.copyarea.CopyAreaLockedException:
Copy area "/Users/vizmacmini2/Jenkins/jenBranch941u1_vizmacmini2" is
locked by another process. Retry the request once that operation
completes. Lock info: last-refreshed:Nov 14, 2013 5:38:02 PM
locked-on:Nov 14, 2013 4:41:07 PM user-id:vizmacmini2
hostname:10.197.40.115 process-id:unknown." conflict
If the file is locked because of a process keeping an handle on it, it can be as simple as killing that process, and relaunching the update through the CCRC Navigator View
Refresh > Update from Repository
Regarding a ""com.ibm.rational.clearcase.remote_core.copyarea.CopyAreaLockedException" error message, the IBM help page mentions:
The Copy Area Locked prompt appears when ClearCase encounters a copyarea.lck file after a user has attempted to rebase or deliver from a ClearCase Remote Client that resides on the same machine as the ClearCase native client.
So I suspect that your script need to find and remove that copyarea.lck file, in order to proceed.
But I would also recommend to check why (or if) there is a pending rebase or deliver in progress.
It would be best if that "rebase or deliver" was fully completed before your script runs.
The OP jingxw adds in the comments:
The progress is pending because of last progress is fail due to a timeout or manually quit. So the lock is expected.
Related
Hi,
I am getting the below error when trying to update my view . Also, creds manager service is stopped and not getting started.
As long as the credmanager.exe is not started, none of the view (snapshot or dynamic) will work. So you need to debug that first.
Typically, you would check the ClearCase logs, and the Windows event, to see what the issue is. See "how to fix or investigate 'Operation “view_ws_is_ws_view” failed'?", using cleartool getlog.
That kind of error ("This application has failed to start becauselibatriaks.dllwas not found. Re-installing the application may fix this problem") was seen with rather old versions of ClearCase (7.0.1).
See for instance this thread.
If the DLL is present and the directory is in your path you should never
get this error.
Check to see how far ...\rational\clearcase\bin is down your SYSTEM path, and make sure the DLL's are in there.
ccgzip.exe will be called (by the client process) when checking in any files that fall back to the "compressed_file" element type. It may be called by the view server during file opens and checkouts to construct cleartext if needed. The former uses your user path, the latter will normally use the SYSTEM path.
We've seen odd behavior on Windows when the path gets >500 characters
long, though there seems to be no "official" limit to the length this environment variable (%PATH%) can grow to.
The error message you see is likely a path issue. Whether that's related to the other issue is unknown...
Is the albd server process running? The credential manager service is flagged to depend on this service. If that service fails to start, or terminates, the credential manager service will also fail.
A service startup failure should be in the Application or System Event logs. and from there the "Troubleshooting albd startup failures" technote on ibm.com would likely be a good place to start.
My internet connection often fails, causing a Putty disconnect and Vim creating swap files. When I come back and recover, I never get the "(D)elete" option when reopening the file, even if I close the session and restart. What am I doing wrong?
Most likely the vim process is still open that has the same process ID as the old vim session (or the pid got recycled, unlikely). You should see something like process ID: 37675 (still running) on one of the lines (seventh line for me), if you do then the delete option won't be there since vim thinks that the owning vim session is still open.
You should kill the other vim session since it still seems to be running. If vim does not detect the something with the process id is open it will offer the delete option and just show, process ID: 37675
Another option would be to run inside something like tmux or screen, if you get disconnected you can always reconnect to your old session once you are sshed back into the machine.
Every time I try to copy clearcase file from view location to another location, it generates the following error:
The file cannot be opened because it is being used by another process.
Please close all applications that might access this file and try again.
Any ideas why this is happening?
That explains probably your previous question: some process must keep an handle on the files you want to copy.
Try to close as many apps as you can, or even try that copy just after a reboot.
That is not a ClearCase issue. Its totally Windows one. You need not to close all apps to find the lock. try to install the "unlocker" application it will notify you what is locking your process
http://download.cnet.com/Unlocker
Enjoy,
Eli
I have a very strange error today on windows ClearCase.
I encounter the following error while delivering from my old stream to the parent stream.
Meanwhile I made a new child stream on windows and delivered from there and it was OK.
The most amazing thing is I used the same old stream on unix and delivery completed without any problem.
What might be the reason behind this failure of my old stream on windows?
Do you wish to continue with this deliver operation? [no] yes
cleartool: Warning: Trigger "dlvr_start_pre" has refused to let deliver_start proceed.
cleartool: Error: A deliver_start preop trigger does not allow this operation.
cleartool: Error: Unable to do integration.
cleartool: Error: Unable to deliver stream "...".
You need to find that "dlvr_start_pre" script and see what it does.
This isn't a script automatically put by ClearCase: it has been written and put in place by your ClearCase admin, in a path accessible form any Windows workstation.
But you also need to consider your current ClearCase client.
For instance, "non-interactive triggers fail with warning about interactivity using CCRC or CCWeb".
That old stream could also have been created with different rights (owner/group) than the new one (that happens if the CLEARCASE_PRIMARY_GROUP environment variable changes)
when i execute cleartool mkbl it hangs and never returns. The window has to be killed and restart.
what might be the possible reasons behind it and how do I fix it?
Since UCM cleartool mkbl put a baseline on all modified components, that means that, behind the scene, it will call mklabel.
And that can takes time, if there are a lot of new or modified files to labelled, one by one.
If this isn't the issue, then you need to check the logs (both of the client and the server), in order to see if all the necessary services are in place (like the albd server, the lock manager, ...).
You can use cleartool getlog for that.