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 IC84496 Status: Geschlossen

DiagLevel=0 in db2cli.ini doesn't have any effect. 'Event'
msg logging in db2diag.log is not needed when DiagLevel=0 on client

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1                       * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Problem first fixed in Version 10.1 Fix Pack 1
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
14.06.2012
14.11.2012
14.11.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList