DB2 - Problem description
Problem IT36199 | Status: Closed |
POSSIBLE DB2FMP TRAP IN SQLQG_FMP_RUNTIME_OBJECT::GET_RSTATE_INFO() WHEN RUNNING FEDERATED QUERY | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
With multiple Federated queries running it is possible to have a db2fmp trap in sqlqg_FMP_Runtime_Object::get_rstate_info(). The signs of this would be a db2fmp A failure that you would see reported in the db2diag.log A connection failure for example leading to the db2fmp A termination. The trap might occur a bit later in a db2fmp B with the following top stack: 0x00002AAAB670A6B8 sqlqg_FMP_Runtime_Object::get_rstate_info + 0x0038 0x00002AAAB6719065 sqlqg_FMP_FindRuntimeObject + 0x0065 0x00002AAAB67145D7 sqlqgRouter + 0x00e7 0x00002AAAB6714152 sqlqg_fedstp_hook + 0x0082 0x00002AAAAC232DE7 sqlqgDyload + 0x00f7 0x00002AAAABCB6DE2 sqlerFedFmpListener + 0x0f12 0x00002AAAABCBF0A2 sqlerWorkerThreadEntry + 0x03f2 ...l | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to 11.5.6 or later * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to 11.5.6 or later * **************************************************************** | |
Comment | |
Upgrade to 11.5.6 or later | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.03.2021 21.06.2021 21.06.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |