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

INITIAL CONNECTION ERRORS LIKE -4499 ARE NOT COLLECTED IN DIAGNOSTIC DATA
THROUGH DB2.JCC.DIAGLEVELEXCEPTIONCODE SETTING

product:
DB2 CONNECT / DB2CONNCT / B50 - DB2
Problem description:
When initial connection establishment fails with error -4499,
error is not capture in diagnostic log when the property to
collect diagnostics only for particular error codes is set.

e.g:
db2.jcc.diagLevelExceptionCode=-4499
db2.jcc.dumpDiagLevel=1
db2.jcc.outputDirectory=C:\JCC\Workspaces\logs

When the application is executed with above properties set(e.g
in DB2JccConfiguration.properties file), and if application
receives -4499 error, no diagnostics file is generated under
location set to db2.jcc.outputDirectory.

The expected behavior is that the logs must be generated only
for -4499 error under the location db2.jcc.outputDirectory.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Db2 JCC Users                                                *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 V11.5.8.0 or later                            *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* Db2 JCC Users                                                *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 V11.5.8.0 or later                            *
****************************************************************
Comment
Problem fixed in Db2 V11.5.8.0
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.11.2021
07.10.2022
24.10.2022
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)