home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC77322 Status: Geschlossen

SQL_ATTR_DESCRIBE_OUTPUT_LEVEL WHEN SET AS 3 , THE SQLGETCONNECTATTR STILL
SHOWS AS 0

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Steps to reproduce 
 
opt callerror on 
opt echo on 
writeini common DescribeOutputLevel 3 
quickc 1 1 TEST123 
sqlsetconnectattr 1  SQL_ATTR_DESCRIBE_OUTPUT_LEVEL 2 
sqlgetconnectattr 1  SQL_ATTR_DESCRIBE_OUTPUT_LEVEL 
sqlsetconnectattr 1  SQL_ATTR_DESCRIBE_OUTPUT_LEVEL 3 
sqlgetconnectattr 1  SQL_ATTR_DESCRIBE_OUTPUT_LEVEL 
killenv 1 
 
 
Output 
 
> sqlsetconnectattr 1  SQL_ATTR_DESCRIBE_OUTPUT_LEVEL 2 
SQLSetConnectAttr: rc = 0 (SQL_SUCCESS) 
> sqlgetconnectattr 1  SQL_ATTR_DESCRIBE_OUTPUT_LEVEL 
SQLGetConnectAttr: rc = 0 (SQL_SUCCESS) 
Option (Unknown) = 2 
Output length = 4 
> 
> sqlsetconnectattr 1  SQL_ATTR_DESCRIBE_OUTPUT_LEVEL 3 
SQLSetConnectAttr: rc = 0 (SQL_SUCCESS) 
> sqlgetconnectattr 1  SQL_ATTR_DESCRIBE_OUTPUT_LEVEL 
SQLGetConnectAttr: rc = 0 (SQL_SUCCESS) 
Option (Unknown) = 0 
Output length = 4 
> 
 
Ideally when 3 is given the sqlgetconnectattr should be giving 3 
and not 0.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* When application program uses CLI.                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* SQL_ATTR_DESCRIBE_OUTPUT_LEVEL WHEN SET AS 3 using           * 
* SQLSetConnectAttr, THE SQLGetConnectAttr  STILL SHOWS IT AS  * 
* 0.                                                           * 
*                                                              * 
* > sqlsetconnectattr 1  SQL_ATTR_DESCRIBE_OUTPUT_LEVEL 3      * 
*                                                              * 
* SQLSetConnectAttr: rc = 0 (SQL_SUCCESS)                      * 
*                                                              * 
* > sqlgetconnectattr 1  SQL_ATTR_DESCRIBE_OUTPUT_LEVEL        * 
*                                                              * 
* SQLGetConnectAttr: rc = 0 (SQL_SUCCESS)                      * 
*                                                              * 
* Option (Unknown) = 0                                         * 
*                                                              * 
* Output length = 4                                            * 
*                                                              * 
* >                                                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to db2_v97fp5 or later releases.                     * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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

Lösung
db2_v97fp5 fixes the issue and after fix SQLGetConnectAttr will 
show the correct value.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.07.2011
12.12.2011
12.12.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
9.7.0.5 FixList