suche 36x36
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 IT16208 Status: Closed

SQLSYNTAXERROREXCEPTION WAS THROWN WHEN SQL WAS EXECUTED USING CACHED
PREPAREDSTATEMENT.

product:
DB2 JDBC SQLJ D / DB2DSDRVR / A50 - DB2
Problem description:
SqlSyntaxErrorException was thrown when SQL was executed using 
cached PreparedStatement.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users using driver release older than 3.69 and above     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* 1)JCC threw SqlSyntaxErrorException  when SQL was executed   * 
* using cached PreparedStatement.                              * 
* 2)when the cached statement is re-executed, driver uses a    * 
* cursor name that does not match the correct  cursor that it  * 
* wants to update.                                             * 
* 3)This throws second cursor -510 error.                      * 
* 4)This issue has been fixed in RTC 89320                     * 
*                                                              * 
* Code modification has done and the defect has been fixed and * 
* released in V10.5. This fix is for  LUW T4 connection        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade the DB2 10.5 fixpack 8                               * 
****************************************************************
Local Fix:
Solution
upgrade the DB2 10.5 fixpack 8
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.07.2016
22.02.2017
22.02.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)