更新ClearCase快照视图时出错 [英] Error while updating ClearCase snapshot view
问题描述
我有一个用户（只有一个，其他所有用户都很好）试图更新其ClearCase视图。
直到今天，它已经为他们服务了6个月。
I have one user (only one, all the others are fine) trying to update their ClearCase view.
It has worked for them for the last 6 months up until today.
更新时，他们得到：
Unable to read directory "." Permission denied
Errors were encountered in loading "\VOB"
I做了一个 gpresult ，看来他们在正确的组中，并且信息流没有为他锁定。
CC Doctor不会来
自从他上周五使用CC以来，什么都没有改变。
I did a "gpresult" and it seems like they are in the correct groups and the stream is not locked for him.
CC Doctor isn't coming up with any errors either.
Nothing has been known to change since he last used CC on Friday.
还有其他地方我应该吗？
Are there any other places that I should look?
I'm out of ideas and I believe I have reached the end of my google search...
推荐答案
通常要检查的元素是：
- 环境变量
CLEARCASE_PRIMARY_GROUP - 视图的特征：
cleartool lsview -l -full -pro viewTag
由于用户未进行任何更改，因此可以将其链接到Windows p rofile问题。确保重启后问题仍然存在。
Since the user hasn't made any changes, it can be linked to a Windows profile issue. Make sure that the issue persists after a reboot.
还要确保没有Windows组策略更改或登录特权演变（例如撤销了管理员权限），这可以解释为什么用户无法阅读ClearCase快照视图的根目录。可能是Windows ACL问题（即与ClearCase不直接相关。
Also make sure there isn't a Windows group policy change or login privilege evolution (like an admin right revoked) which could explain why the user isn't able to read the root directory of the ClearCase snapshot view. It could be a Windows ACL issue (ie not directly related to ClearCase.
OP报告说，由< a href = http://www-01.ibm.com/support/docview.wss?uid=swg21135509 rel = nofollow noreferrer> CLEARCASE_PRIMARY_GROUP ClearCase不再考虑该组，因为该组不在用户注册的前32个Windows组中。
The OP reports that the group referenced by CLEARCASE_PRIMARY_GROUP wasn't taken into account anymore by ClearCase, because that group wasn't in the first 32 Windows groups the user was registered to.
技术说明 关于CLEARCASE_GROUPS变量详细介绍了正确的解决方法：
The technote "About the CLEARCASE_GROUPS variable" details the right workaround:
此变量用于抵消 SUNRPC协议由ClearCase使用，因此，属于32个以上Microsoft Windows组（域或本地）成员的任何用户都可能遇到访问问题。
This variable is used to counteract a limitation in the SUNRPC protocol that is used by ClearCase whereby any user who is a member of more than 32 Microsoft Windows groups (domain or local) can run into access problems.
如果任何用户都存在用户环境变量 CLEARCASE_GROUPS ，ClearCase将在确定时首先考虑该变量的值中指定的以分号分隔的组列表。 （或显示）用户所属的组。
If the user environment variable CLEARCASE_GROUPS exists for any user, ClearCase will consider the semicolon-separated list of groups specified in the value of this variable first when determining (or displaying) which groups a user belongs.
本质上，当您登录Windows时，会收到 访问令牌 。
ClearCase将按照Windows提供的顺序处理这些令牌（完全
达到32个组后，ClearCase将停止处理令牌。
In essence, when you log in to Windows, you receive an Access Token.
ClearCase will process these tokens in the order Windows provides them (which is completely random and cannot be configured in any way).
ClearCase will stop processing the tokens after 32 groups have been reached.
CLEARCASE_GROUPS 变量是解决此问题的唯一方法。
设置了变量后，ClearCase将按照写入列表的顺序查看 CLEARCASE_GROUPS 列表中的每个组名，并将其与提供的Windows访问令牌进行比较。
如果组名与Windows Access令牌中的组匹配，则ClearCase将为该组创建一个ClearCase访问令牌。
The CLEARCASE_GROUPS variable is the only way to work around this behavior.
When the variable is set, ClearCase will look at each group name in CLEARCASE_GROUPS list in the order the list was written and compare that to the Windows Access Tokens provided.
If the group name matches a group in the Windows Access Token, then ClearCase will create a ClearCase Access Token for that group to use.
当CLEARCASE_GROUPS变量用尽时， ClearCase将返回Windows Access Token列表，所有尚未添加到ClearCase令牌的组将按照提供的顺序从其余列表中添加，直到使用Windows令牌中的所有组（如果低于32） ）或达到32组限制。
When the CLEARCASE_GROUPS variable is exhausted, ClearCase will go back to the Windows Access Token list, and any group that has not already been added to the ClearCase token, will be added from the remaining list in the order provided, until all groups in the Windows token are used (if below 32) or the 32 group limit is reached.
这篇关于更新ClearCase快照视图时出错的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
