home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IT02478 Status: Geschlossen

NULLPOINTEREXCEPTON WHEN THERE IS A PROBLEM IN ACCESSING JCCDIAG.LOG

Produkt:
DB2 DATA SRVR D / DB2DSDRVR / A10 - DB2
Problembeschreibung:
It is is seen that if the driver has a problem in accessing the 
jccdiag.log file when trying to write to it, a 
NullPointerException may occur. 
 
One scenario where this issue is seen involves the driver 
performing a server side license check. The driver receives a 
SQLCODE -805 from the DB2 server. The driver tries to log this 
failure to jccdiag.log. The driver fails to obtain a valid 
outputstream to the jccdiag.log file and suffers a 
NullPointerException.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of IBM Data Server Driver for JDBC and SQLJ        * 
* shipped with DB2 10.1 releases earlier than DB2 10.1 Fixpack * 
* 5                                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Refer error description                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 Fixpack 5                                * 
****************************************************************
Local-Fix:
Lösung
Upgrade to DB2 10.1 Fixpack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
12.06.2014
22.07.2015
22.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList