This technote provides possible causes for permission denied errors during an IBM® Rational® ClearCase® merge operation, including UCM deliver or rebases along with steps to resolve the problem.
If there are no Read Permissions on the element, the following errors may appear during merge operations:
Unable to determine absolute pathname for "M:\myview\myvob\sub\aaa.txt@@\main\4" - Permission denied
Unable to access "M:\myview\myvob\sub\aaa.txt@@\main\4": Permission denied.
Run the cleartool describe -long <file> command to display output showing if the user has read permission for the version or not.
%>cleartool describe -long aaa.txt
created 21-Jul-05.12:40:11 by user@domain
User : IBM-KECP07Z\user : --- <== NO READ
Group: IBM-KECP07Z\group : r--
Other: : r--
element type: text_file
predecessor version: \main\7
There are permission problem on the storage container.
Run the cleartool checkvob -protection -pool <.vbs> (where .vbs is the path to the VOB storage) command to see if the output indicates if there is a permission error regarding a VOB container for the element.
Note: Review the IBM Rational ClearCase Command Reference Guide on the topic of checkvob (cleartool man checkvob) for more details.
Resolving The Problem
Add read permissions to the element.
Run cleartool protect -chmod u+r <file> to add a read permission, then retry the merge.
Note: Review the IBM Rational ClearCase Command Reference Guide on the topic of protect (cleartool man protect) for more details.
Fix the protections on the storage container.
Run cleartool checkvob -fix -protection -pool <.vbs> (where .vbs is the path to the VOB storage) to correct the permission problem.
Also, review the steps in technote 1142606 for more information on using the fix_prot utility to reprotect the VOB storage.
29 September 2018