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 IC81519 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 / 970 - 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 9.7 Fix pack 6                        * 
****************************************************************
Local Fix:
available fix packs:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem first fixed in Version 9.7 Fix pack 6.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC84496 IC84511 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.02.2012
22.06.2012
22.06.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList