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

EXESSIVE ENTRY IN DB2DIAG.LOG AFTER RUN DB2PD -HADR COMMAND

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
In db2diag.log there can be seen excessive message after run 
 
  db2-d -d SAMPLE -hadr 
 
2016-12-30-11.22.45.206727+060 I40479877E296         LEVEL: 
Event 
PID     : 41159                TID : 47073953742720  PROC : 
db2pd 
INSTANCE: db2inst1               NODE : 000 
HOSTNAME: hostname.org 
FUNCTION: DB2 UDB, RAS/PD component, pdHADR, probe:10 
START   : db2pd -hadr started 
 
TSA monitors db2 via this command and this cause filling up 
db2diag.log
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher               * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
First fixed in DB2 11.1 Mod 2 Fix Pack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.01.2017
27.06.2017
27.06.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)