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

WARNING MESSAGE FROM DB2AGENT GETS REPORTED TO DB2DIAG.LOG PERSISTENTLY

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Warning message from db2agent PERFDB gets reported to 
db2diag.log persistently in DB2 version 10.5 FP4 and 10.5 FP5 
 
Example of the message: 
 
2015-01-30-10.07.47.316323-360 E20024813A447        LEVEL: 
Warning 
PID     : 35061784             TID : 47548          PROC : 
db2sysc 0 
INSTANCE: db2opm05             NODE : 000           DB   : 
PERFDB 
APPHDL  : 0-16555              APPID: *LOCAL.db2opm.150409075651 
AUTHID  : DB2OPM             HOSTNAME: db2opmp 
EDUID   : 47548                EDUNAME: db2agent (PERFDB) 0 
FUNCTION: DB2 UDB, license manager, sqllcRequestAccess, probe:0
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All platforms affected.                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v10.5 Fixpack 7 or later.                 * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 LUW v10.5 Fixpack 7.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.03.2015
02.02.2016
02.02.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList