APAR status
Closed as Permanent restriction.
Error description
ClearQuest Client gets the error when a long name (32 - 50 bytes ) action is executed. The issue likely happens just after upgrading a schema and its u ser database. Because the ClearQuest Designer GUI validates if the length of a ction name is maximum 25 characters, NOT maximum 25 Bytes. On multibytes system environment (e.g. Japanese OS). the ClearQu est Designer is able to create an action name with up to 25 doub le-bytes (50 bytes). The PK50734 was closed as no plan to fix, However, the ClearQues t Designer GUI must validate if the length of action name is max imum 25 Bytes, in order to prevent this issue with ClearQuest Cl ients on production server. This is why this APAR has been creat ed. Error message: ERROR! SQLExecDirect RETCODE=-1, State=S1000, Native Error=12899 SQL statement='insert into history (dbid.entity, dbid.entitydef _id, entityde_name, user_name, action_timesstamp.old_state, new_ state.comments) values (33554505, 33554435,16777224,'Defect','ad min',' ?? 25 Japanese characters HERE ?? ', {ts '2009-03-05 21:5 9:02'}, 'Submitted','Submitted', 'AP1 +09:00')' [DataDirect][ODBC Oracle Wire Protocol driver][Oracle]ORA-12899: value too large for column 'CQJAUSER'.'HISTORY','ACTION_NAME' ( actual:50, Maximum:30) Steps to reproduce the issue: On Windows Japanese. 1) In ClearQuest Designer, Open DefectTracking Schema. 2) create a new action with (32 - 25 character long Japanese) in the Defect recored type. 3) check in it and upgrade the user DB (SAMPL). 4) In ClearQuest Client ( Windows, RCP, Web), Create a record an d Use the action. 5) The error occurred, the user could not execute the action at all.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** ClearQuest gets the error when a long action name (32 - 50 bytes) is executed. The issue likely happens just after upgrading a schema and its user database.
Problem conclusion
Due to higher priority change requests, we have no plans to address this change request in the next 18 months. The effort and risk associated with fixing this problem is too significant. Please consult with the following technote: http://www-01.ibm.com/support/docview.wss?uid=swg21273006
Temporary fix
Comments
APAR Information
APAR number
PK82821
Reported component name
CLEARQUEST WIN
Reported component ID
5724G3600
Reported release
701
Status
CLOSED PRS
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-03-18
Closed date
2012-01-24
Last modified date
2012-01-24
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH5A","label":"Rational ClearQuest"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
24 January 2012