DB2 - Problem description
Problem IT36444 | Status: Closed |
SETTING DB2_DPS_RLOG_SHR_MEMBYTES CAUSES EXCESSIVE AMOUNT OF INFORMATION IN DB2DIAG.LOG | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
Turning on DB2_DPS_RLOG_SHR_MEMBYTES causes an entry in db2diag.log every time a new scan is opened. Some jobs close and reopen scans over and over, which can cause a large number of db2diag.log entries of the form: 2021-04-02-03.20.58.438760+120 E1824A551 LEVEL: Info PID : 3146242 TID : 38296 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-75 APPID: 192.168.0.157.55260.210331100726 AUTHID : db2user1 HOSTNAME: myhost EDUID : 38296 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, data protection services, sqlpgReadLogCalculateShredderScanMemory, probe:19180 DATA #1 : DB2_DPS_RLOG_SHR_MEMBYTES=63554432 in effect This APAR will move this "Level: Info" report in db2diag.log from DIAGLEVEL 3 to DIAGLEVEL 4 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Using ReadLogAPI * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to version 11.5 mod 4 fix pack 0 * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Using ReadLogAPI * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to version 11.5 mod 4 fix pack 0 * **************************************************************** | |
Comment | |
First fixed in version 11.5 mod 4 fix pack 0 | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 02.04.2021 06.04.2021 06.04.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |