重新格式化时出错
我正在将 vob 从 Solaris 迁移到 RHEL，在 24 个 vobs 中，除了 1 个 pvob 出现以下错误外，23 个 vob 已成功迁移。
db_dumper.54: Error: Unexpected error from database library (8) in "../db__dump.c" line 2835
db_dumper.54: Error: Error from libdb (8)
cleartool: Error: Could not dump database.
cleartool: Error: Trouble dumping versioned object base "/vobstg/pvob.vbs".
dbcheck status,
Processing delete chain: 0 records on delete chain.
Processing records:
100%
Database consistency check completed
0 errors were encountered in 0 records/nodes
Check for HyperSlink and got following error cleartool checkvob -hlinks -hltype hltype:HyperSlink vob:/vob/pvob
cleartool: Error: Hyperlink type not found: "HyperSlink".
陷入迁移困境
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
它可以帮助了解
dp_dumb在错误退出之前处于哪个阶段，例如 此帖子。但通常的做法是压缩锁定 pvob 内容，并将其发送给 IBM 进行分析。
HyperSlinks 在这里不是问题（就像在制作副本）。
正如IBM 支持线程中提到的：
It can help knowing at what stage the
dp_dumbwas before exiting in error, like in this thread.But the usual course of action is to compressed a locked pvob content, and send it to IBM for analysis.
The HyperSlinks aren't an issue here (as they would when making a replica).
As mention in this IBM support thread:
问题是活动中的特殊字符，IBM 给了我工具来修复它。现在一切正常了。
Issue is with special character in activity, IBM gave me tool to fix it. Now things are normal.