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

DB2DIAG.LOG INFO MESSAGES FROM DELIVERBUFFERTOTARGETCHANNEL ARE NOT
NECESSARY WHEN THERE IS NO DISCARD REASON

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The db2diag.log will show messages as follow: 
 
2010-10-07-10.09.43.386713-180 I2220E530           LEVEL: Info 
 
PID     : 3789                 TID  : 47446369495360PROC : 
db2sysc 1 
INSTANCE: xxxx               NODE : 001          DB   : xxxxx 
 
APPHDL  : 0-3318               APPID: AC11D215.GD55 
 
AUTHID  : xxxxxx 
 
EDUID   : 297                  EDUNAME: db2agntp 1 
 
FUNCTION: DB2 UDB, fast comm manager, 
sqkfFastCommManager::DeliverBufferToTarg, probe:51 
MESSAGE : Discard reason: 
 
DATA #1 : Hexdump, 4 bytes 
 
0x00002B26F7FFB9D4 : 0000 0000 
.... 
 
This messages are dumped when diaglevel is set to 4. The number 
of entries in the db2diag.log might be significant under some 
circumstances. Leading to performance problems at the instance 
level.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users in V9.7                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The db2diag.log will show messages as follow:                * 
*                                                              * 
* 2010-10-07-10.09.43.386713-180 I2220E530          LEVEL:Info * 
* PID    : 3789                TID  : 47446369495360PROC       * 
* :db2sysc 1                                                   * 
* INSTANCE: xxxx              NODE : 001          DB  : xxxxx  * 
* APPHDL  : 0-3318              APPID:  <application-id>       * 
* AUTHID  : xxxxxx                                             * 
* EDUID  : 297                  EDUNAME: db2agntp 1            * 
* FUNCTION: DB2 UDB, fast comm manager,                        * 
* sqkfFastCommManager::DeliverBufferToTarg, probe:51           * 
* MESSAGE : Discard reason:                                    * 
* DATA #1 : Hexdump, 4 bytes                                   * 
* 0x00002B26F7FFB9D4 : 0000 0000                               * 
* ....                                                         * 
*                                                              * 
* This messages are dumped when diaglevel is set to 4. The     * 
* number of entries in the db2diag.log might be significant    * 
* under some                                                   * 
* circumstances. Leading to performance problems at the        * 
* instance level.                                              * 
*                                                              * 
* The size of the db2dig.log will increase rapidely.           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply V9.7 fix pak 4                                         * 
* or,                                                          * 
* Lower DIAGLEVEL to 3                                         * 
****************************************************************
Local Fix:
Change DIAGLEVEL to 3 
 
UPDATE DBM CFG USING DIAGLEVEL 3
available fix packs:
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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 V9.7 fix pak 4
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC72894 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.10.2010
24.05.2011
24.05.2011
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList