查看完整版本: CQ升级时报错

CQ升级时报错

CQ升级时报错 报错信息如下
版本为 2002.05.00  
只改动了一下一个脚本

在IBM网站上查了一下
解决办法如下：
This error is known to occur if the ClearQuest database is not at the current feature level (metaschema). To resolve this issue, check to see if the metaschema has been upgraded to the latest version. Although ClearQuest has new packages available, the database metaschema might not have that value until it has been upgraded.
可是没有看明白到底怎么解决

回复 沙发 的帖子

IBM提供的信息的意思是，你的数据库的feature level偏低，你必须将你的master数据库的feature level升级到更高的才能进行一些最新的package的操作

如果问题真是这样，你可以尝试这样做：
1. 打开CQ Maintenance Tool，选中目标connection
2. 右击改connection，选择Upgrade，在后面的步骤中会看到Feature Level，选择最新的Feature Level6，下一步直到完成。

（以上是基于CQ7.0或CQ7.0.1，老的版本中好像没见到有这个概念）

打开CQ Maintenance Tool去升级  可是报
the specified schema repository doesn't need to be upgraded
大家谁遇到这种情况呀  现在解决都无从下手

回复 地毯 的帖子

如果不能升级，那错误原因可能就不是Feature Level了

不懂，向各位学习中。

大家考虑一下  有什么其他原因可能产生这个错误吗 ？

回复 7# 的帖子

你对schema做了啥修改？

有没有更改记录类型的名称？

没有就只是增加了一个动作而已
然后就报错 现在把那个动作删除了
升级 同样报错  快疯掉了

回复 9# 的帖子

试试将最新的schema version删除掉，然后重新做修改

一些package都是在打补丁的时候有的。是不是需要打补丁？

有按图片说明做过吗？
1.co the schema again
2.Make a small change and the undo that change
3. Successfully validate the schema
4. Ci the schema
5. Upgrade user database again
有没什么效果？

按照yunshan的办法恢复回去
然后重新更改 checkin  问题依旧  然后排除 发现增加了一个动作
然后恢复回去 不增加动作 改动其他 升级OK  然后 增加动作 升级报错
不明白为什么不能增加动作
然后报错后按照 scmtata的想法 升级报错  
查找SQL数据库，发现entityenf中缺少记录类型的记录

换个新高一点的版本吧，那个太旧维护多费劲啊。::em42::

回复 14# 的帖子

没有办法  只能用这个 我早就想升级了
老大不让

我们直接从2003.06.00升级到7.0大概用了一年了也没有出现什么大的问题,
主要是这个版本人们已经开始不熟悉了.::em57::

大家还有没有好的办法啊
我现在一点头绪都没有了

Problem(Abstract)
This technote explains how to resolve the error: The user database upgrade was not completely successful, when upgrading a user database in IBM? Rational? ClearQuest?.  
  


Cause
One cause of this error is renaming the Defect record type. Full text of the error message is as follows:


The user database upgrade was not completely successful. The
package queries could not be installed to the user database. The
most possible reason is that one or more of the packages used by
the schema are not correctly registered by the machine. It is
recommended NOT to use the user database until you perform
following steps.
* Check out the schema again.
* Successfully validate the schema.
* Upgrade user database again.
The actual error message was:
***Print Report Format, Public Queries\PrintReportFormats\Defect
associated by record type Defect, not installed.  The association
has been edited by user. Continuing...

  

Resolving the problem
Note: Performing the steps listed in the error above will result in the same error. If the user tries to delete the report formats from the user database, they will reappear the next time that they login to that user database.
To resolve this issue:

Determine which schema is being used. View the schema summary in ClearQuest Designer (View > Schema Summary). Select version 1 of the schema and see which Setup package and the version is listed. For example, DefectTrackingSetup 4.0 or UnifiedChangeManagementSetup 5.0.
On the computer where the upgrade is failing, navigate to the ClearQuest directory. Open the packages folder. Find the Setup package (found in Step 1) and then open up the version of the package. Here you will see a package.ini file.
Note: The UnifiedChangeManagementSetup package is listed in the directory as UCMSetup.
Make a copy of the package.ini file and rename it so that you have an original copy.
Open the package.ini file and find the line:

ReportFormats=PrintReportFormats\EmailRule;PrintReportFormats\
Customer;
PrintReportFormats\Project;PrintReportFormats\User;
PrintReportFormats\Defect

Note: This line is found after the line QueryFiles=. The line above may look different depending on the Setup package that you are viewing. For example, the same line in the UnifiedChangeMangementSetup package is:

ReportFormats=PrintReportFormats\EmailRule;PrintReportFormats\
User;PrintReportFormats\Defect;PrintReportFormats\UCMProject;
PrintReportFormats\BaseCMActivity;PrintReportFormats\
UCMUtilityActivity

Delete the Print Report Formats out of this line of text. Do not delete the ReportFormats= portion of this line of text. This line will now only appear as ReportFormats=.
Note: Make sure that you do not delete any more than this line (like the Reports=
line of text found underneath).
Next, go to the last entry in the package.ini file (Reports= This is found under the line of text reading ReportFormats=. For the DefectTrackingSetup package:

Reports=
[PrintReportFormat]
RecordTypes=Defect,Email_Rule,Customer,Project,Users
Defect=Public Queries\PrintReportFormats\Defect
Email_Rule=Public Queries\PrintReportFormats\EmailRule
Customer=Public Queries\PrintReportFormats\Customer
Project=Public Queries\PrintReportFormats\Project
Users=Public Queries\PrintReportFormats\User


The UCMangementSetup package would look like:

Reports=
[PrintReportFormat]
RecordTypes=Defect,Users,UCM_Project,BaseCMActivity,
UCMUtilityActivity,Email_Rule
Defect=Public Queries\PrintReportFormats\Defect
Email_Rule=Public Queries\PrintReportFormats\EmailRule
Users=Public Queries\PrintReportFormats\User
UCM_Project=Public Queries\PrintReportFormats\UCMProject
UCMUtilityActivity=Public Queries\PrintReportFormats\UCMUtilityActivity
BaseCMActivity=Public Queries\PrintReportFormats\BaseCMActivity

Delete everything in this entry EXCEPT for:
Reports= (starting at [PrintReportFormat] to the end of the text). The entry will now only appear as Reports=.
Save the modified copy of the package.ini file.
You will now be able to upgrade your user database.
在IBM上找到这样一个解决方案
可是打开package.ini和他说的完全不一样呀  郁闷死了

建议先升级到 2003.06.15, 然后再升级到更高版本

回复 19# 的帖子

如果不升级 还有其他办法吗？？