|
Problem IC64427
|
Status: Closed |
STRING VALUE IN STORED PROCEDURE RESULT SET HAS EXTRA SPACE WHEN DISPLAYED FROM DB2 CLP |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
When calling a stored procedure from the DB2 CLP, a string value
in the result set displays one more extra space.
For example, if a column in the result set is defined as
VARCHAR(255), the value displayed to the screen will be the
string value padded by extra spaces up to a length of 256.
There should only be padded spaces up to a length of 255. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Could occur on v95 and later releases. All platforms, *
* easilyreproducible. *
****************************************************************
* PROBLEM DESCRIPTION: *
* When calling a stored procedure from the DB2 CLP, a *
* stringvaluein the result set displays one more extra *
* space.For example, if a column in the result set is defined *
* asVARCHAR(255), the value displayed to the screen will *
* bethestring value padded by extra spaces up to a length of *
* 256.There should only be padded spaces up to a length of *
* 255. *
****************************************************************
* RECOMMENDATION: *
* upgrade to db2_v95fp6 or db2_v97fp2 or later releases. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
db2_v95fp6 contains the fix of this issue, as a result the user
will get padded spaces up to a length of 255. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC64443
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.11.2009
30.06.2010
30.06.2010 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
