|
Problem IC77834
|
Status: Closed |
SQLCOLUMNS() API IS NOT RETURNING DISPLAY SIZE FOR THE COLUMN_SIZE COLUMN FOR UDTS |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When the SQLColumns() API call is used to retrieve column
information for a User Defined Type (UDT) against a Linux, Unix
or Windows server, the size that is being returned is the size
derived from they SYSIBM.SYSDATATYPES system catalog table.
This table contains the storage length for the UDT as opposed to
the display length of the base type.
By default DB2 should be returning the display length of the
base type of a UDT unless the CLI statement attribute
SQL_ATTR_RETURN_USER_DEFINED_TYPES is set to TRUE.
The SQLColumns() API invokes a stored procedure on DB2 for
Linux, Unix, Windows. This APAR is to fix the stored procedure
on the database server to ensure it returns the display length
of the base type by default. Therefore this is a server-side
fix. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* see Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7, Fixpack 5 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 9.7, Fixpack 5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.07.2011
21.12.2011
21.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
