Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC87080 Status: Closed

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

product:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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.
available fix packs:
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

Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.10.2012
03.01.2013
03.01.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList