DB2 - Problem description
Problem IT09414 | Status: Closed |
EXTENSIVE DB2DIAG.LOG LOGGING IN SQLPSCANHISTFILEFORRECOVERYLIST AND SQLPSHRTHROTTLEWORKER | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
DB2 might perform extensive logging in sqlpScanHistFileForRecoveryList and sqlpshrThrottleWorker functions. Symptoms are messages logged in the db2diag.log every 30 seconds: 2015-05-13-00.30.07.342453+120 I114504A507 LEVEL: Warning PID : 26785 TID : 89847 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-6826 APPID: 10.10.10.10.52204.150512132146 AUTHID : DB2INST1 HOSTNAME: node01 EDUID : 89847 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, data protection services, sqlpScanHistFileForRecoveryList, probe:3955 MESSAGE : Log recovery list is loaded. 2015-05-13-00.30.07.838636+120 I115012A518 LEVEL: Info PID : 26785 TID : 144926 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-6826 APPID: 10.10.10.10.52204.150512132146 AUTHID : DB2INST1 HOSTNAME: node01 EDUID : 144926 EDUNAME: db2shred (SAMPLE) 0 FUNCTION: DB2 UDB, data protection services, sqlpshrThrottleWorker, probe:2000 DATA #1 : <preformatted> shredder worker 0 waiting for master. This APAR change is to reduce logged entries to necessary ones. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.5 fixpack 7 * **************************************************************** | |
Local Fix: | |
N/A | |
Solution | |
Problem was first fixed in DB2 version 10.5 fixpack 7 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 11.06.2015 20.01.2016 20.01.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 |