|
Problem IC64766
|
Status: Geschlossen |
SQLCODE -805 OCCURS ON THE NEXT SQL FOLLOWING A RESET OF JDBC CONNECTION FOR AN APPLICATION RUNNING UNDER WAS |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
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-Zusammenfassung: |
****************************************************************
* 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 |
| verfügbare FixPacks: |
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
|
| Lösung |
Please move to fix pack 1 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 24.11.2009
29.04.2010
30.04.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.2
|
 |
