DB2 - Problem description
Problem IT18449 | Status: Closed |
SHOULD NOT DUMP "PDDIAGREADFROMFILEINTOBUFFERBS, PROBE:25" WITH DIAGLEVEL 3 | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
Can see a new message that is dumped in db2diag.log every time PD_GET_DIAG_HIST() function is called: 2016-06-16-14.31.29.896451+120 I16404886A861 LEVEL: Info PID : 10289404 TID : 38609 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-55555 APPID: *LOCAL.db2inst1.160616122823 AUTHID : DB2INST1 HOSTNAME: db2host EDUID : 38609 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, RAS/PD component, pdDiagReadFromFileIntoBufferBS, probe:25 MESSAGE : Initial status when binary serach : DATA #1 : unsigned integer, 8 bytes 16404885 DATA #2 : String, 53 bytes 2016-06-15-00.00.00.000000:2016-06-16-00.00.00.000000 DATA #3 : String, 26 bytes 2016-06-16-00.00.00.000000 DATA #4 : String, 0 bytes Object not dumped: Address: 0x000000012B28F5D4 Size: 0 Reason: Zero-length data DATA #5 : String, 53 bytes 2016-06-15-00.00.00.000000:2016-06-16-00.00.00.000000 This was intended as a serviceability request, but you can see these messages too many times and ask that we only log it with DIAGLEVEL 4. | |
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 | |
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 : | 16.12.2016 23.06.2017 23.06.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |