1

我需要一些帮助。两年前，我接手了维护我们的 ClearCase 系统的职责，该系统已经非常过时了，而我之前完全没有使用它的经验。今天，用户在从我们的两台 ClearCase 服务器中检出文件时遇到问题，我什至不知道从哪里开始。我搜索了互联网无济于事。我运行了以下命令来尝试对其进行故障排除，但我现在被卡住了，我不知道从哪里开始。

以下是用户尝试签出文件时发生的情况：

cleartool co Makefile
Checkout comments for "Makefile":
.
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Unable to locate versioned object base with object id:"e2a51855.b3f511d3.ad28.00:01:80:8e:4e:e8".
cleartool: Error: Trouble finding the global definition for local type "development".
cleartool: Error: Unable to check out "Makefile".

我环顾四周，似乎无法找到解决此问题的方法。
这些特定服务器运行的是旧版本的 RedHat (Linux 3.10.0-123)；而且我发现的日志没有给我足够的信息来知道下一步该做什么。我们的 ClearCase 版本是 8.0.1.5

以下是我为尝试解决问题而运行的各种命令的结果：

[vobadm@lgbuild3] cleartool desc /vob/admin_vob
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
Non-MVFS directory "/vob/admin_vob"
  Modified: Thu 16 Dec 1999 03:10:58 PM EST
  Protection:
    User : vobadm   : rwx
    Group: eng      : r-x
    Other:          : r-x

最后，我读到 VOB 可能被锁定，但是当我运行解锁命令时会发生这种情况：

[vobadm@lgbuild3]$ cleartool unlock /vob/admin_vob
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Unable to access "/vob/admin_vob": error detected by ClearCase subsystem.

根据 VonC，我运行了以下命令，结果如下：

[vobadm@lgbuild3 log]$ ct descr -l vob:/vob/admin_vob
cleartool: Error: Unable to determine VOB for pathname "/vob/admin_vob".
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Error from VOB database: "/vob/admin_vob".
cleartool: Error: Trouble opening VOB database: "/vob/admin_vob".
cleartool: Error: Unable to determine VOB for pathname "/vob/admin_vob".

任何关于我下一步应该看哪里的帮助或指导将不胜感激。

4

2 回答 2

0

It depends on your version of ClearCase and OS (for ClearCase server and client), but the four main command you need to look at are:

First, you can describe your vob, to check its associated ACL (owner/group), as I did here:

cleartool descr -l vob:/vobs/vobtag

Then you can check the same for your user views, as in here:

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

Depending on the rights you see, you might need to fix_prot the vob itself (maybe even protectvob if you need additional groups.
Or simply fix_prot the views to make them compatible with the main group of the Vob.

For the error:

cleartool: Error: Unable to determine VOB for pathname "/vob/admin_vob"._vob

You need to at least create a tag for that vob:

ct mktag -vob -tag /vob/admin_vob -pub -password clearcase -host yourVobServer -gpath /shared/path/to//vob/admin_vob.vbs /shared/path/to//vob/admin_vob.vbs
于 2020-07-25T19:32:15.950 回答
0

第一条消息有一个可能很重要的线索：

cleartool: Error: Unable to locate versioned object base with object id:"e2a51855.b3f511d3.ad28.00:01:80:8e:4e:e8".

你应该运行

cleartool lsvob -long /vob/admin_vob

或者

{cc install}/rgy_check -vobs

VOB 可能未注册。这不应该发生......但是......如果VOB在NAS上，您可能会很幸运并且只需要cleartool register -vob {vob storage path}使用-host和-hpath运行或等效。

您还应该查看 VOB 服务器上的 db_server 日志以查看是否有其他消息。最简单的方法是转到 vob 服务器主机（ssh、本地登录等）并打开 /var/adm/rational/clearcase/log/db_server_log。或者，在您收到错误后立即cleartool desc vob:/vob/admin_vob运行cleartool getlog -host {vob server name} db

这至少会让你开始。在不知道幕后实际发生的情况下，我无法提供太多建议，并且由于处理我的工作的各种原因，在我们知道之后我无法详细说明，但我至少可以提供指针和其他问题.

你说得对，8.0.1.5 已经过时了。8.0.1.x 自 2018 年 4 月 30 日起不再支持。当前版本为 9.0.1.10 和 9.0.2.1（或 2）。如果您还在使用 ClearQuest，则必须迁移到 9.0.2.x 才能升级到当前版本，因为 CQ 9.0.1.0 不再可供下载。

此问题与 CC 的旧版本无关，但您可能需要与支持人员合作才能解决此问题，这可能需要升级到受支持的版本。

于 2020-07-26T15:59:30.863 回答