DB2 - Problembeschreibung
Problem IC62901 | Status: Geschlossen |
INCORRECT DISPLAY SIZE RETURN FOR SQLEXTENDEDESCRIBE WITH ROW TYPE PARAMETER WITH > 8 FIELDS IN LINUX,WINDOWS FOR CLIDESC BCKT | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
When using DB2 CLI driver, CLI API SQLExtendedDescribe returns different display sizes on differentplatforms for ROW data type. However, display size should be same on all platforms. ex When a stored procedure with 3 parameters is called for AIX the display size obtained is 3 as expected.But on the linux and nt32 modes the obtained display size is 2 when the expected value is 3 for ROW data type. However with all other data types correct display sizes are obtained. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * CLI driver DB2 v97 * **************************************************************** * PROBLEM DESCRIPTION: * * When using DB2 CLI driver, CLI API SQLExtendedDescribe * * returns * * different display sizes on * * * * differentplatforms for ROW data type. * * * * However, display size should be same on all platforms. * * * * * * * * ex When a stored procedure with 3 parameters is called * * for * * AIX the display size obtained is 3 as expected.But on the * * linux * * and nt32 modes the obtained display size is 2 when the * * expected * * value is 3 for ROW data type. * * * * However with all other data types correct display sizes * * are * * obtained. * **************************************************************** * RECOMMENDATION: * * Upgrade to V97FP1 * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 UDB version v97 FP1 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 01.09.2009 22.02.2010 22.02.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP1 | |
Problem behoben lt. FixList in der Version | |
9.7.0.1 |