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 IC64766 Status: Closed

SQLCODE -805 OCCURS ON THE NEXT SQL FOLLOWING A RESET OF JDBC CONNECTION
FOR AN APPLICATION RUNNING UNDER WAS

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
SQLCODE -805 occurs on the next SQL following a reset of JDBC 
 
It appears that the IBM JDBC Driver is not handling the 
currentPackagePath setting correctly "after the connection 
reset".
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* SQLCODE -805 OCCURS ON THE NEXT SQL FOLLOWING A RESET OF     * 
* JDBC                                                         * 
* CONNECTION FOR AN APPLICATION RUNNING UNDER WAS              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* SQLCODE -805 occurs on the next SQL following a reset of     * 
* JDBC                                                         * 
*                                                              * 
*                                                              * 
* It appears that the IBM JDBC Driver is not handling the      * 
*                                                              * 
* currentPackagePath setting correctly "after the connection   * 
*                                                              * 
* reset".                                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please move to fix pack 1                                    * 
****************************************************************
Local Fix:
N/A
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Solution
Please move to fix pack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.11.2009
29.04.2010
30.04.2010
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList