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和他说的完全不一样呀 郁闷死了
