I got the following error while trying to complete the posted delivery. Is there anything I can do it from the target site?
cleartool: Error: Unable to check out
"/vobs/amit_sumit/lost+found/pcs_i_ltf_odfc_set_sftp.c.842f38e667011e395ad0018fe6508eea".
cleartool: Error: Some files could not be checked out in the target view.
cleartool: Error: Unable to perform merge.
cleartool: Error: Unable to do integration.
cleartool: Error: Unable to deliver stream "banglore_atx_cl".
Yes.
You can change the config spec of the view you are using for your deliver in order to not select the lost+found folder.
cd /path/to/my/view
cleartool edcs
Add (as a first rule, at the top)
element /vobs/amit_sumit/lost+found -none
save and resume your deliver.
Note: depending on what you are merging (a folder within the vob, or the vob itself), you also can add same same selection rule between:
#UCMCustomElemBegin - DO NOT REMOVE - ADD CUSTOM ELEMENT RULES AFTER THIS LINE
#UCMCustomElemEnd - DO NOT REMOVE - END CUSTOM ELEMENT RULES
But by putting it on top, you are sure it will be taken into account.
That lost+found elements will still be part of the deliver, but will be skipped with a warning, as opposed to be blocking.
Related
I have created a symbolic link (see below) to a version controlled file from a different vob (VOB_II) and the file is visible from a dynamic view whereas it’s not visible from the UCM snapshot view.
A.txt --> ..\..\..\VOB_II\SampleDir\A.txt
I have the following selection and load rules.
element \VOB_II\SampleDir\A.txt ...\branch1\LATEST
load \VOB_II\ SampleDir
Any ideas why the file is not getting loaded in the snapshot view? I could not figure out what’s wrong. Any help or inputs are much appreciated.
First, do a cleartool ls in C:\path\to\my\view\VOB_II\SampleDir
The status can explain why the element is not loaded.
Typically, you need selections rules that selects also the parent folders (SampleDir and Vob_II) before being able to select A.txt.
I would recommend at least adding an element * /main/LATEST (stop rule)
element \VOB_II\SampleDir\A.txt ...\branch1\LATEST
element * /main/LATEST
load \VOB_II\ SampleDir
Second, it looks like you are trying to load the actual A.txt (the one in VOB_II\SampleDir\A.txt), and not the symbolic link one the A.txt pointing to ..\..\..\VOB_II\SampleDir\A.txt
I don't know where is that symbolic link A.txt. In Vob_I?
Third, see "Symbolic links in snapshot views"
Snapshot views created from Linux or the UNIX system maintain standard symbolic link behavior.
In the context of loading a snapshot view, links are treated as:
VOB links (those that point to objects inside the VOB) and
non-VOB links (those that point outside the VOB).
Hard VOB links are followed; symbolic links are copy-created.
If a VOB link cannot be resolved, an error results.
Non-VOB links are resolved, if possible, but it is not an error if they cannot be resolved.
Snapshot views created from a Rational ClearCase host running Windows software do not support links.
VOB symbolic link behavior is approximated in the following ways:
If a load rule selects a symbolic link, the link target is copied into the view at the link path.
In Clearcase, how do I resolve "loaded but missing" for an element in my snapshot view?
The last thing I did was to delete a branch, for which my config spec was currently using a rule to see.
I've tried deleting the file(rm filename), and updating my snapshot view again, to no avail
Figured it out: I followed the instructions here.
Removed the file(rm file.cpp).
'cleartool get -to /path/to/snapshot/view/file.cpp file##/main/myBranch/LATEST'
Next, the file was hijacked, so I did a cleartool update but specified to "Rename hijacked files and load selected version from the VOB" as instructed in the instructions here,
When I execute a "cleartool ls filename##specificVersion", I see
filename [not loaded]
What does this mean?
For background information, I was trying to also execute a cleartool mkbranch, and was a "Element not found" error. So, for a sanity check, I tried a cleartool ls.
"not loaded" means the file:
is selected (by the selection rules element * ...) but:
not loaded by the load rules (load /xx/yy...)
You can see both sets of rules by doing a cleartool catcs anywhere within your view (or cleartool edcs to edit said rules)
This is typical of a snapshot view, which is the only one having "load rules" (as opposed to a dynamic view)
See:
"Before accessing files not loaded into snapshot views":
A snapshot view contains only the set of elements that you specify in the load rules of your view. (In UCM, by default, your view loads all of your project source files.)
When you restrict the scope of a view, it contains only a subset of elements in the VOB. During the course of a development cycle, you may need to see a version of an element that is not loaded into your snapshot view.
You can view nonloaded files or copy them into your view for build purposes, but you cannot check them out. Only file elements that are loaded into your view can be checked out.
"To copy a nonloaded element into a snapshot view"
cleartool get -to filename path
cleartool get -to prog.c.previous.version prog.c##/main/v3.1_fix/10
My company uses ClearTeam Explorer for version control. Sometimes when either I or a co-worker apply a label, we get an error message. Today my comrade got
"An error occurred during a ClearCase operation.
CRMAP7009: CCRC command "WriteProperties" failed:
CCRC WANServer: Error: No permission to perform operaton "change event".
CCRC WAN Server:Error: Mustbe one of : user associated with event, object owner, element owner, VOB.."
According to the above message, you would think the operation failed, correct?
However, it appears looking at a random sampling of the files that everything was labeled correctly.
It is alarming to get this message and then find out it appears to have done what it said it didn't??? - There will always be lingering doubt unless you can verify that every single file was labeled properly.
Early on, I ignored this error and continued making labels for various versions. Now, I want to verify because I have lots of GB of files and there is no way I can hand verify everything.
Offhand, it seems like I want to make a view based on the date the label was created (maybe months ago) and then have a script to show any files that don't have a label.
Comparing files between 2 labels might work also provided at least one of the labels has "all the files" labeled?
Any guidance is appreciated.
According to the above message, you would think the operation failed, correct?
No, and there is an APAR PM79463 in progress on that one.
(an APAR is an Authorized Program Analysis Report, or APAR, that is: "a formal report to IBM development of a problem caused by a suspected defect in a current release of an IBM program")
(CTE = " ClearTeam Explorer")
Error description
User tried to apply label to an element on CTE, and error messages were shown although label was applied.
So user tried to apply label to an element on HomeBase in native client after logging in Windows as the same user as user who was used in CTE, and succeeded to apply label without errors.
If executed user is not the owner nor creator of the object but belongs the same group of VOB owner, the issue was occurred on CTE although the operation was succeeded on HomeBase.
Error messages are shown on pop up window as follows.
CRMAP7009: CCRC command 'WriteProperties' failed:
CCRC WAN Server Error: no permission to perform operation 'change event'
CCRC WAN Server Error: Must be one of : user associated with event:
object owner, element owner, VOB owner, member of ClearCase group
So you can try and put labels through the ClearCase HomeBase gui, which seems more robust.
In Clearcase I have a VOB with a path like this:
\Department\ProductGroup\Product1\Development
I have a view with a Config Spec like this:
element * CHECKEDOUT
element * .../mybranch/LATEST
element * /main/LATEST -mkbranch mybranch
load \Department\ProductGroup\Product1
All the source code for Product1 is in the Development directory. Nothing I care about exists outside this directory. All references in the code are relative to this directory.
I have created the above Clearcase view in the directory c:\dev
Presently the above setup creates a directory:
c:\dev\Department\ProductGroup\Product1\Development
All the parent directories to Development are empty. I'd rather have just the following directories.
c:\dev\Product1
Where c:\dev\Product1 mapped to the VOB path \Department\ProductGroup\Product1\Development. Is this possible?
1/ Why not only load \Department\ProductGroup\Product1\Development ?
load /Department/ProductGroup/Product1/Development
Note: you can use '/', easier than '\' and Windows config spec does interpret it correctly.
1bis/ If you want to keep a general rule, you could use some "cleaning rules"
Consider this config spec
(test it in a dynamic view first, to check quickly -- that is without endless update reloading steps -- if the result does match what you need: files under Development and no files anywhere else)
element * CHECKEDOUT
# read/write selection rule for the directory and sub-directory
# where you need to work
element /Department/ProductGroup/Development/... .../mybranch/LATEST
element /Department/ProductGroup/Development/... /main/LATEST -mkbranch mybranch
# specific selection rule for the parent directories of Development
# those rules do not contain a mkbranch directive
element /Department/ProductGroup .../mybranch/LATEST
element /Department/ProductGroup /main/LATEST
element /Department .../mybranch/LATEST
element /Department /main/LATEST
# cleaning rule right there: anything outside /Department/ProductGroup/Development
# will not be selected, hence not loaded
element /Department/* -none
load \Department
That way, you always keep the same load rule load \Department, and your selection rules do the cleaning for you.
2/ Regarding your path issue, you can use Symlink but the easiest way is to use a subst
subst X: c:\dev\Department\ProductGroup\Product1\Development
And you could go on using your snapshot view within X:\
BUT that would not work because ClearCase needs:
view.dat (the hidden file indicating a directory tree is in fact a snapshot view)
a vob (which is Department in your case. ProductGroup\Product1\Development is a path within the Vob Department)
X:>ct lsview -l -full -pro -cview
cleartool: Error: Cannot get view info for current view: not a ClearCase object.
X:>ct ls
cleartool: Error: Pathname is not within a VOB: "."
For those same reasons, a hardlink with Junction on windows will not work:
c:\dev>junction Product1 Department\ProductGroup\Product1
Junction v1.05 - Windows junction creator and reparse point viewer
Copyright (C) 2000-2007 Mark Russinovich
Systems Internals - http://www.sysinternals.com
Created: C:\dev\Product1
Targetted at: C:\dev\Department\ProductGroup\Product1
C:\cc\xxx>ct ls
cleartool: Error: Pathname is not within a VOB: "."
So what you can do is:
subst X: c:\dev
That combined with the specific load rules from 1/ or the cleaning rules from 1bis/ will give you:
a slightly shorter path
no extra empty sub-directories
2bis/ "Devious" solution:
From the ClearCase explorer, move Development from Department\ProductGroup\Product1 to Department! That move will be recording within 'mybranch' version tree, and will not be visible for anyone else working in /main/LATEST.
Then with the subst from above, you will work within 'mybranch' in Department\Development.
X:\Department\Development
When you want to go public, make the inverse move.