DB2 - Problem description
Problem IT31783 | Status: Closed |
POSSIBLE TRAP (SEGV) WHEN RUNNING A QUERY ON A NICKNAME POINTINGTO A FEDERATED SOURCE AND FEDERATED GOES DOWN. | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
To qualify the query should be including a table located on a remote federated source. Query example: select col1 ... from tab_nickname where ... Where 'tab_nickname' is a nickname to a table in a federated server. If that federated source goes down OR if the application is forced we might trap. The stack of the trap can vary but most likely will be under a 'fetch'. For example: 0x000010000EFA51C0 sqlrifisBuffFetch + 0x03d0 0x000010000EFA4CA4 sqlriFetch + 0x0194 0x000010000EE36168 sqlrieoqp + 0x05c8 0x000010000F0D4A00 sqlriftr + 0x00e0 0x000010000F053DE0 sqlriSectInvoke + 0x0410 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All Db2 LUW users * **************************************************************** * PROBLEM DESCRIPTION: * * To qualify the query should be including a table located on * * a * * remote federated source. Query example: * * * * select col1 ... from tab_nickname where ... * * * * Where 'tab_nickname' is a nickname to a table in a federated * * server. * * * * If that federated source goes down OR if the application is * * forced we might trap. * * The stack of the trap can vary but most likely will be under * * a * * 'fetch'. For example: * * * * 0x000010000EFA51C0 sqlrifisBuffFetch + 0x03d0 * * 0x000010000EFA4CA4 sqlriFetch + 0x0194 * * 0x000010000EE36168 sqlrieoqp + 0x05c8 * * 0x000010000F0D4A00 sqlriftr + 0x00e0 * * 0x000010000F053DE0 sqlriSectInvoke + 0x0410 * **************************************************************** * RECOMMENDATION: * * Fixed in future fixpacks. * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
Comment | |
NA | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 06.02.2020 24.04.2020 24.04.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |