When updating my clearcase (snapshot) view I get the following symlink errors:
Unable to resolve symlink
"setups.cmd". The symlink
target will not be loaded.
Unable to resolve symlink "setup.sh".
The symlink target will not be loaded.
Unable to resolve symlink
"setupwithdomain.doc". The
symlink target will not be loaded.
What do I do or tell my admin to do to get rid of this errors.
Are you on Windows? And with which ClearCase version
There is this IBM Technote, which explains why attempts to create an IBM Rational ClearCase symbolic link on Microsoft® Windows in ClearCase Explorer from a snapshot view fails when the snapshot view root is created with a lower case drive letter.
But that would only be for CC2003.
This thread mentions a similar issue:
We have had problems resolving symlinks when loading snapshot views.
It appears that the resolution of the pathname to the linked file is case sensitive.
The solution for us was to ensure that all symlinks used the correct case for the pathname to the linked file.
Related
I get this error while I try to load a new snapshot view with my own config spec (this is base ClearCase).
cleartool error: Unable to load "filename.exe": no version selected in configuration
specification.
If I try to load a dynamic view with the same config spec - I can
see this file (that can't be loaded). The selected version does exist on the config spec (of the snapshot view as well).
If I change the config spec of the snapshot view (to default config spec) I can load all files with no problem (but on the other hand, the missing file is not loaded since it's not part of the config spec).
What goes wrong? Can you advice please?
Thank you
The easiest way to debug this is to do a:
cd /path/to/snapshot/view/avob/parent/directory
cleartool ls
cd /path/to/dynamic/view/avob/parent/directory
cleartool ls
That allows to check:
the status of the file in both views
if the other files in that folder are selected with the same versions.
I am using following version of clearcase -
Rational ClearCase Remote Client Version: 7.1.2
In my attempt to checkout files and folders recursively, I read these links:
How do I perform a recursive checkout using ClearCase?
http://www.ibm.com/developerworks/rational/library/4687.html
The issue is I am not able to locate these bin files used in these articles:
cleartool.exe not located in (c:\Program Files\Rational\ClearCase\bin\cleartool.exe)
clearmenuadmin.exe not located in (C:\Program Files\Rational\ClearCase\bin\clearmenuadmin.exe)
Not to mention windows search could not locate any of these files in C:\Program Files.
Please suggest what I am missing here ?
You cannot use cleartool commands with CCRC, only the GUI and CCRC/Teamapi (as in "Rational clear case CM API fail to checkout source code").
The CCRC is a ClearCase Remote Client, with none of the executables of a full ClearCase client.
Maybe the simplest way is to use Use "Environment -> ClearCase Search" GUI, to search for all elements, and select them all to checkout them.
I am trying to upgrade the commons-lang-2.0.jar to commons-lang-2.4.jar. When trying to add the 2.4 jar to the source control Clear Case is throwing the following error:
An element with this name (commons-lang-2.4.jar) has ALREADY been created in ClearCase for
this directory [lib], may be in a different version history of this directory that the one
you are seeing.
Review the version history of this directory [lib] to find it.
I feel this is because commons-lang-2.0 jar is existing in the lib folder and before adding 2.4 i need to remove 2.0. Can someone tell me if I am right? If so How can i remove 2.0 jar and replace it with 2.4?
That looks like a warning about "evil twins", in which your file commons-lang-2.4.jar was added, then removed from lib (and you would add it again, creating a new element with the same name, but a completely separate history: evil twin)
See also "Evil twin problem and subtractive merge".
See "About Evil twin" to try and find which version of lib already contains your file commons-lang-2.4.jar.
Once you have found the right version of lib, you can merge it to your current version of lib, restoring the deleted commons-lang-2.4.jar.
In our clearcase we are having few folders require same contents.
We use to have symlink to achieve that. But Now our folders are having view private files, so symlink doesn't do any good.
Is copying it again the only mechanism ?
Any other policy or settings which can help to symlink view private file?
Symlinks (OS symlinks, not cleartool symlinks) should be supported, even for private files (they would certainly work in snapshot view anyway: those are based on the native OS).
Otherwise, copy is still a solution to fallback on.
But I am not aware of any dedicated policy on ClearCase for symlinks on private view files.
The is only one policy for versionned symlinks (created by cleartool ln -s, but this isn't your current scenario):
On Linux and UNIX systems, symbolic links are listed as absolute pathnames by default.
To list symbolic links as relative pathnames, set the environment variable CCASE_LS_RELATIVE_SYMLINK_PATH.
The OP Samselvaprabu mentions using Dynamic view drive and i am in windows environment, and reports the following error on symlink creation:
Object Msilist.bat is not a valid symlink target; no symlinks will be created.
Please select only valid symlink targets and retry the operation.
The man page "To create a Vob symlink" mentions the following restrictions:
You can use the cleartool ln -s command to create a VOB symbolic link (symlink) to the following items:
A file or directory (checked in or checked out)
A symbolic link
An eclipsed element (dynamic views only)
A hijacked element (snapshot views only)
The target of the symbolic link must be in the same view as the directory in which the symbolic link is to be created.
If you are in a snapshot view, unloaded elements are not valid symlink targets. Also, the directory in which the symlink is to be created must also be loaded.
My point was:
If cleartool ln -s doesn't work, especially for private file (which are not in ClearCase anyway), use OS symlink (in your case, NTFS symlinks if you are on Windows Vista or more, otherwise simple junction points)
So OS symlinks (native symlinks, not created by cleartool) should work.
I have CM Server for ClearCase Remote Clients in windows 2003 server.
Installed package in server.
I'm getting below error in CCRC client:
"CRVAP0087E CCRC command "checkin" failed: Unable to create pathname for
file "C:\ccweb\v973012\v973012_Latest_FMC": Permission denied"
Can you please help me to fix this issue?
The most efficient way to troubleshoot right issue is to go directly to the CCRC server, under the CCRC web (snapshot) view and type:
cd c:\ccweb\v973012
cleartool lsview -l -full -pro -cview
That way, you see with which group the user has created the CCRC view in the first place.
That group must be one of the groups associated with the Vob of the element being checked-in.
Check also this technote:
During the installation of Rational ClearCase, you are asked for a temporary directory to use during the installation to unzip large artifacts.
This temporary directory is used to preserve user configuration settings during an update or uninstall process.
If you specify a directory that is mounted on a file system that is separate from the installation directory, the file permissions and owners are not preserved when the files are moved across the file systems.
Finally, check for any trigger set on the Vob: they can have an unwanted side-effect with that CCRC 'checkin' operation.
In the specific case of the OP mth123, he suggests:
Go to the Windows Explorer and try these steps:
Go the the following directory: C:\ccweb
Rename the folder v123412 to V123412 (Only change the first letter and put "V" capitalized.)
Check if the problem is solved.
So depending on the actual tag of the view, this could be an issue about case-sensitive path.
The latest patch caused this issue. While applying patch CC preserving some file inclusing ccweb folder. while restoring those folder during post install these directory might have changed with lowercase/upper case. This is currently with IBM queue.
If you are going to upgrade CCRC please make a copy of ccweb directory with proper ACL or use ccopy.exe (clearcase utility)