DB2 - Problem description
Problem IT05141 | Status: Closed |
MULTIPLE AGENTS WORKING WITH SAME VARIATION CAN FLOOD DB2DIAG.LO G WITH | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
It is a timing issue if two agents access same variation and first agent delete it or could not insert it and at the same time second agent looks for the same variation but could not find it, Will dump warning message in the db2diag.log. 2014-10-10-20.14.01.526244+000 I3608E638 LEVEL: Warning PID : 19721 TID : 140458697156352 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : Sample APPHDL : 0-8062 APPID: *LOCAL.DB2.* AUTHID : DB2INST1 HOSTNAME: Localhost EDUID : 31 EDUNAME: db2agent (Test) 0 FUNCTION: DB2 UDB, access plan manager, sqlra_find_var_var, probe:850 DATA #1 : String, 113 bytes Unexpectedly unfilled after wait; marked invalid p_stmt anchor_id: 955 p_stmt stmt uid: 5182 env_id: 1 var_id: 1 2014-10-10-20.14.31.420770+000 I4247E638 LEVEL: Warning PID : 19721 TID : 140335560779520 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : Sample APPHDL : 0-8067 APPID:*LOCAL.DB2.* AUTHID : DB2INST1 HOSTNAME: Localhost EDUID : 143 EDUNAME: db2agent (Test) 0 FUNCTION: DB2 UDB, access plan manager, sqlra_find_var_var, probe:850 DATA #1 : String, 113 bytes Unexpectedly unfilled after wait; marked invalid p_stmt anchor_id: 955 p_stmt stmt uid: 5185 env_id: 1 var_id: 1 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.1 Fix Pack 5 * **************************************************************** | |
Local Fix: | |
It can be safely ignored. | |
Solution | |
First fixed in DB2 10.1 Fix Pack 5 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.10.2014 17.02.2017 17.02.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.5 |