Fixes are available
APAR status
Closed as fixed if next.
Error description
If tracked field names are defined that exceed the 30 byte column name length limit on Oracle, then the process of updating tracking definitions for the Performance Data Warehouse will fail while attempting to create or add column names for tracked fields. Tracked field names that contain DBCS characters are more susceptible to this issue since multiple bytes are needed to represent a DBCS character.
Local fix
When defining names for Performance Data Warehouse tracked fields that contain DBCS characters, create names with ten or fewer characters so that the 30 byte Oracle column name length limit will not be exceeded.
Problem summary
**************************************************************** * USERS AFFECTED: Users of BPM Express, BPM Standard, and * * BPM Advanced. * **************************************************************** * PROBLEM DESCRIPTION: Updating tracking definitions for the * * Performance Data Warehouse fails due * * to an attempt to create a database * * column on Oracle with a name that * * exceeds the 30 byte column name * * length limit for Oracle. * **************************************************************** * RECOMMENDATION: * **************************************************************** String length validation of Performance Data Warehouse tracked field names did not properly consider DBCS characters to ensure that all database column names generated were under 30 bytes in length. The issue has been resolved by truncating the database column name for a tracked field at 30 bytes in length. In addition, a configuration property has been added that makes it possible to choose the point where the tracked field name is truncated in order to create the corresponding database column name. Remaining space after the truncation point and before the 30 byte limit is used add an integer at the end of the column name for uniqueness if needed. Following is an example of the new configuration property. <max-column-name-length>27</max-column-name-length> There are a few considerations related to setting the max-column-name-length property. -It is best to pick an integer value that is a multiple of three, such as 27 or 24. -If more than ten tracked fields related to a tracking group start with the same characters, then it would be best to set a 24 byte truncation point to allow more room for the integer that is added at the end for uniqueness. This property must be set in the 100Custom.xml file for the Performance Data Warehouse; following is an example of a section to add to the 100Custom.xml file. <properties> <performance-server merge="mergeChildren"> <max-column-name-length merge="replace">Value, such as 27 or 24</max-column-name-length> </performance-server> </properties> The following documentation section explains where the 100Custom.xml configuration files are located: http://pic.dhe.ibm.com/infocenter/dmndhelp/v8r0m1/topic/com.ibm. wbpm.admin.doc/topics/managing_twks_config_settings.html. Note that the "server_type" replaceable value should be performance-data-warehouse for the Performance Data Warehouse. This issue has been addressed as part of IBM Business Process Manager 8.0.1 Fix Pack 2.
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
JR47485
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
801
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-08-12
Closed date
2013-11-06
Last modified date
2013-11-06
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
R800 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
07 January 2022