Fixes are available
APAR status
Closed as program error.
Error description
When accessing an Oracle Warehouse Database using ODBC if a column is defined as WCHAR, the data maybe truncated. The problem might be seen as charts not displaying data correctly, change to a table view and check the timestamps and verify the century, year, month, hour, minute, second, numbers are all present. If some of the numbers are truncated, the timestamp can't be parsed correctly for the chart (i.e. x axis can't be plotted). Instead of In the case of this report, the timestamp column was being identified by the ODBC driver as type SQL_WCHAR. It is still unknown why the ODBC driver was identifying the column as WCHAR since that is not the way the Warehouse Proxy Agent would have defined it. In any case, this brought out a bug where the data would get truncated. The KFW_SQL_OCTET_LENGTH_WVARCHAR_ONLY=N environment variable was recommended as a work around, but this brings out a second bug which makes numeric data undisplayable. Both problems need to be corrected.
Local fix
None at this time
Problem summary
When a database column is defined as wide (i.e. SQL_WCHAR, SQL_WVARCHAR, and SQL_WLONGVARCHAR), the length is the number of characters, not necessarily the size of the buffer. The length used should be the OCTET_LENGTH provided by the ODBC driver for that column. Since the portal server did not use the correct buffer size when the type was either SQL_WCHAR or SQL_WLONGVARCHAR, the data to be truncated. This problem can only occur on the portal server running on Windows when ODBC is used to get data from the warehouse database.
Problem conclusion
The code was changed to use the correct buffer size for SQL_WCHAR and SQL_WLONGVARCHAR. It was already using the correct size for SQL_WVARCHAR. The fix for this APAR is contained in the following maintenance packages: | interim fix | 6.2.0.3-TIV-ITM-IF0002
Temporary fix
Comments
APAR Information
APAR number
IZ59326
Reported component name
TEPS
Reported component ID
5724C04PS
Reported release
620
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-08-26
Closed date
2009-09-17
Last modified date
2009-10-07
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
TEPS
Fixed component ID
5724C04PS
Applicable component levels
R620 PSY
UP
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"620"}]
Document Information
Modified date:
30 December 2022