更新视图时出现错误 [英] Getting error while updating the view

问题描述

更新视图时遇到错误。

检索视图同步和数据时遇到问题。

Problems were encountered while retrieving view synchronization and data.

Clearcase CM server error: Unable to access "vob name" : unknown error in vob
Clearcase CM server error: Error 2 config spec load rule problems encountered 

如何解决该错误消息？

推荐答案

您需要访问日志（本地或在服务器上）以了解更多信息。

以前是 cleartool getlog （ClearCase 7.x，即使对于CC 8.x ）

You need to access the logs (both locally or on the server) to know more.
It used to be cleartool getlog (ClearCase 7.x, even for CC 8.x)

cleartool: Error: Checkout is currently disabled for element "element_name".
Its config spec rule information is currently unavailable due to either an aborted update or an update in progress

类似于在本技术说明中 的较旧CC（7.0.x）：

That is similar to an older CC (7.0.x) described in this technote:

可能的症状1：

如果当前不存在更新，变基或交付操作对于有关视图的进度，错误通常可以归因于视图与流不同步。

Possible cause for symptom 1:

If an update, rebase or deliver operation is not currently in progress for the view in question, the error can often be attributed to the view being out of sync with the stream.

尝试：

cd /path/to/snapshot/view
cleartool setcs -stream

症状2的可能原因：

被劫持的nocheckout意味着在视图中被劫持的版本不再是配置规范选择的版本

Hijacked nocheckout means that the version hijacked in the view is no longer the version the config spec selects from the VOB.

1. 重命名被劫持的文件并更新视图。


2. 章确认被劫持文件的版本。


3. 将被劫持的文件复制到签出的版本上。


4. 从当前版本合并到


5. 现在可以签入该版本。

1. Rename the hijacked file and update the view.
2. Check out the version from which the file was hijacked.
3. Copy the hijacked file over the checked-out version.
4. Merge from the current version to the checked-out version.
5. The version can now be checked in.

可能的症状3：

根据上面提到的错误消息的解释，该问题可能是由于视图的配置规范出现问题或视图更新被中止或不完整引起的。

Possible cause for symptom 3:

Per the error message explanation noted above, the problem may be caused by an issue with the view's config spec or an aborted or incomplete view update.

尝试：

cd /path/to/snapshot/view
cleartool setcs -current

---

（原始答案）

---

(original answer)

这可能是一个正确的问题，如该线程所示。

It can be a right issue, as illustrated by this thread.

检查用户及其用户的组权限两个VOB。

做您依靠 CLEARCASE_PRIMARY_GROUP 环境变量吗？

如果是这样，请检查执行更新的用户的值。

Check group permissions on user and on those two VOBs.
Do you rely on the CLEARCASE_PRIMARY_GROUP environment variable?
If so, check the value of the user performing the update.

将vob的权限与您要更新的当前快照视图的权限进行比较：

Compare the rights of the vob with the ones for your current snapshot view that you are trying to update:

cd /path/to/snapshot/view
cleartool lsview -l -full -pro -cview

如果 CLEARCASE_PRIMARY_GROUP 设置不正确，则更容易：

If the CLEARCASE_PRIMARY_GROUP is not set properly, it is easier to:

• 将其设置为正确的组（即，vob的主要组或次要组之一）


• 删除并重新创建视图。
  
  （如果您不想删除/重新创建视图，您可以修复它）

• set it to the right group (ie the primary group of the vob, or one of the secondary groups)
• delete and recreate your view.
  (if you do not want to delete/recreate your view, you can fix_prot it)

这篇关于更新视图时出现错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！