Fixes are available
Rational ClearQuest Fix Pack 10 (8.0.1.10) for 8.0.1
Rational ClearQuest Fix Pack 11 (8.0.1.11) for 8.0.1
Rational ClearQuest Fix Pack 12 (8.0.1.12) for 8.0.1
Rational ClearQuest Fix Pack 13 (8.0.1.13) for 8.0.1
Rational ClearQuest Fix Pack 14 (8.0.1.14) for 8.0.1
Rational ClearQuest Fix Pack 15 (8.0.1.15) for 8.0.1
Rational ClearQuest Fix Pack 16 (8.0.1.16) for 8.0.1
Rational ClearQuest Fix Pack 17 (8.0.1.17) for 8.0.1
Rational ClearQuest Fix Pack 18 (8.0.1.18) for 8.0.1
Rational ClearQuest Fix Pack 19 (8.0.1.19) for 8.0.1
Rational ClearQuest Fix Pack 20 (8.0.1.20) for 8.0.1
Rational ClearQuest Fix Pack 21 (8.0.1.21) for 8.0.1
Rational ClearQuest Fix Pack 22 (8.0.1.22) for 8.0.1
Rational ClearQuest Fix Pack 23 (8.0.1.23) for 8.0.1
Rational ClearQuest Fix Pack 24 (8.0.1.24) for 8.0.1
Rational ClearQuest Fix Pack 25 (8.0.1.25) for 8.0.1
APAR status
Closed as program error.
Error description
When a ClearQuest user database hosted on an Oracle server is upgraded to feature level 9 the history data seem in forms in all CQ clients shows an unexpected sorting. The history data sorted in two groups. First are listed entries generated after after the feature level upgrade and then the history entries previous to that event. Both groups are correctly (but separately) sorted by action_timestamp. When other databases are used, such as SQL Server, this behavior is not seen. In this cases the history data is listed sorted by action_timestamp from the first to the last entry. For example, in a database that has been upgraded to Feature level 9 on August 1st, the history data for a typical record may display (schematically) as follows: August 2 Modify August 3 Modify August 4 Close July 28 Submit July 29 Modify July 30 Assign July 31 Open Once displayed, the history can be sorted by action_timetamp or any other field clicking on the history control column headers
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * ClearQuest * **************************************************************** * PROBLEM DESCRIPTION: * * ClearQuest history data is not sorted correctly after * * upgrading to feature level 9 on Oracle databases. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
A fix is available in ClearQuest 8.0.1.10. ClearQuest history data is now sorted correctly after upgrading to feature level 9 on Oracle databases.
Temporary fix
Comments
APAR Information
APAR number
PI48272
Reported component name
CLRQUEST MSITE
Reported component ID
5724G3700
Reported release
801
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-09-07
Closed date
2015-12-16
Last modified date
2015-12-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
CLRQUEST MSITE
Fixed component ID
5724G3700
Applicable component levels
R801 PSY
UP
Document Information
Modified date:
15 October 2021