DB2 - Problem description
Problem IT27015 | Status: Closed |
WITH A ROTATING DB2 DIAGNOSTIC LOG, CERTAIN MESSAGES FROM THE DB2HAVEND PROCESS WILL BE LOGGED TO THE DEFAULT DB2DIAG.LOG FILE | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
In the environments where a rotating Db2 diagnostic log is enabled, i.e. where: $ db2 get dbm cfg | grep DIAGSIZE shows a non-zero value, certain messages from db2havend process, which is responsible for the interaction between Db2 engine and high availability software (e.g. IBM TSAMP), will always be logged to the default file named db2diag.log and not the rotating one (one, with a numerical suffix, e.g. db2diag.10.log). This is an example of a message of this kind (note PROC : db2havend): 2018-11-02-05.26.49.624162-420 I2105E413 LEVEL: Event PID : 15235 TID : 47713327275008 PROC : db2havend (db2ha) INSTANCE: db2v111 NODE : 000 HOSTNAME: db2ha1.ibm.com FUNCTION: DB2 UDB, high avail services, db2haEnableResourceGroup, probe:10359 MESSAGE : Issuing unlock request against resource group. DATA #1 : String, 29 bytes db2_db2v111_db2v111_SAMPLE-rg This APAR will address this behavior. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 18.11.2018 16.01.2020 16.01.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |