DB2 - Problem description
Problem IC97832 | Status: Closed |
the db2 registry variable DB2_MAX_THREADS_PER_FMP may not work in a federation environment. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
The db2 registry variable DB2_MAX_THREADS_PER_FMP is used to control the maximum number of db2fmp threads that is allowed to create in a single db2fmp process. However, this variable doesn't work as expected in a federation environment where a db2fmp thread is used to execute a federation query. Once the number of db2fmp threads exceed DB2_MAX_THREADS_PER_FMP, all subsequent db2fmp thread requests fail with -1042 error as below, instead of creating a new thread in a different db2fmp process. 2013-08-19-11.15.02.400335+600 I7236A375 LEVEL: Warning PID : 63176896 TID : 1 PROC : db2fmp (C) 0 INSTANCE: db2inst1 NODE : 000 EDUID : 1 EDUNAME: db2fmp (C) 0 FUNCTION: DB2 UDB, routine_infrastructure, sqlerMasterThreadListener, probe:200 MESSAGE : Max number of thread in fmp reached; no thread created 2013-08-19-11.15.02.400584+600 I7612A574 LEVEL: Warning PID : 459102 TID : 57600 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-225 APPID: 192.168.159.147.39530.130819011602 AUTHID : db2inst1 EDUID : 57600 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, routine_infrastructure, sqlerMasterThreadReq, probe:89 MESSAGE : FMP reported it could not create a new thread DATA #1 : Hexdump, 4 bytes 0x0780000000D6CD80 : 03C4 00C0 .... 2013-08-19-11.15.02.400857+600 I8187A449 LEVEL: Severe PID : 459102 TID : 57600 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-225 APPID: 192.168.159.147.39530.130819011602 AUTHID : db2inst1 EDUID : 57600 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, routine_infrastructure, sqlerGetFmpThread, probe:20 RETCODE : ZRC=0xFFFFFBEE=-1042 2013-08-19-11.15.02.401301+600 I8637A465 LEVEL: Severe PID : 459102 TID : 57600 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-225 APPID: 192.168.159.147.39530.130819011602 AUTHID : db2inst1 EDUID : 57600 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, base sys utilities, sqleFedFMPManager::getFmpFromProcPool, probe:10 RETCODE : ZRC=0xFFFFFBEE=-1042 2013-08-19-11.15.02.401595+600 I9103A462 LEVEL: Severe PID : 459102 TID : 57600 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-225 APPID: 192.168.159.147.39530.130819011602 AUTHID : db2inst1 EDUID : 57600 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, base sys utilities, sqleFedFMPManager::getFmpFromPool, probe:130 RETCODE : ZRC=0xFFFFFBEE=-1042 2013-08-19-11.15.02.402963+600 I9566A469 LEVEL: Error PID : 459102 TID : 57600 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-225 APPID: 192.168.159.147.39530.130819011602 AUTHID : db2inst1 EDUID : 57600 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, Query Gateway, sqlqgFedRbk1, probe:130 MESSAGE : sqlqgFedrollback: skip rollback because not connected! | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users who use fenced mode and muti-connections * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 4. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
With this fix, new fmp process will be created when the connections reach the value of DB2_MAX_THREADS_PER_FMP | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.11.2013 02.06.2014 02.06.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.4 |