| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IC84496 | Status: Closed |
DiagLevel=0 in db2cli.ini doesn't have any effect. 'Event' msg logging in db2diag.log is not needed when DiagLevel=0 on client | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
Two problems: 1) DiagLevel=0 in db2cli.ini doesn't have any effect. The "DiagLevel=0" in db2cli.ini won't be picked up by client process, and the diaglevel still stays at its previous value. 2) After fixing problem 1), then, DiagLevel=0 in db2cli.ini will take effect in client process. Note that when diaglevel is 0, 'Event' messages and admin messages were still captured in db2diag.log. However, on DB2 client side, there is no need to log 'Event' messages when diaglevel is set to 0. Therefore, on client side, when diaglevel is set to 0, we will no longer capture 'Event' messages on db2diag.log Note that after the fix, to totally shut down db2diag.log logging on db2 client side, beside setting "DiagLevel=0" on db2cli.ini, one needs to set "NotifyLevel=0" in db2cli.ini too. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 1 * **************************************************************** | |
| Local Fix: | |
| available fix packs: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
| Solution | |
Problem first fixed in Version 10.1 Fix Pack 1 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 14.06.2012 14.11.2012 14.11.2012 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.1 |
|
| 10.5.0.1 |
|