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

NULLPOINTEREXCEPTON WHEN THERE IS A PROBLEM IN ACCESSING JCCDIAG.LOG

product:
DB2 DATA SRVR D / DB2DSDRVR / A10 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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:
Solution
Upgrade to DB2 10.1 Fixpack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.06.2014
22.07.2015
22.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList