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 IC87080 Status: Geschlossen

SQL0516N AND POSSIBLE DATA TRUNCATION RUNNING QUERY FROM CLI BASED
APPLICATION AGAINST A DB2 FOR Z/OS DATABASE WITH IDAA.

Produkt:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problembeschreibung:
When query acceleration is enabled and a query is ran against 
DB2 for z/OS with IDAA, a CLI based application may receive the 
following error: 
 
SQL0516N  The DESCRIBE statement does not specify a prepared 
statement. 
 
The error may be followed by data truncation in the results as 
well.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All db2 users will effect                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v10.1 FP2 or later                                * 
****************************************************************
Local-Fix:
The problem does not occur when query acceleration is disabled.
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
09.10.2012
03.01.2013
03.01.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.2 FixList
10.5.0.2 FixList