DB2 - Problem description
Problem IT35805 | Status: Closed |
MULTI-THREADED DB2FMP TRAPPED IN SYBASE CALLS INTERMITTENTLY | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
Federation Server with Sybase wrapper calls Sybase Open client routines communicating with a Sybase database. A Multi-threaded Sybase wrapper may call some Sybase routines which are thread-unsafe without serialization under certain conditions, this results in random traps. These routines are cs_ctx_alloc, cs_ctx_drop, ct_init and ct_exit, so the trap stack will have one of them. One typical trap stack: cfg__check_section cfg__parse cfg___load_config comn_init_cfg ct___load_config ct__ctx_cfg ct_init FencedCtlib_Server::initialize_my_server FencedRelational_Server::initialize_server Wrapper::get_server sqlqg_FMP_FindServer sqlqgRouter sqlqg_fedstp_hook sqlqgDyload sqlerFedFmpListener sqlerWorkerThreadEntry start_thread clone The top stacks can be various: cfg__lex cfg__nexttok cfg__parse comn_init_cfg ct___load_config ct__ctx_cfg ct_init cfg__catbuf cfg__add_entry cfg__parse comn_init_cfg ct___load_config ct__ctx_cfg ct_init lm_list_alloc_ex lm_list_alloc cfg__add_section cfg__parse comn_init_cfg ct___load_config ct__ctx_cfg ct_init lm_list_drop lm_list_op comn_drop_cfg cs_ctx_drop __libc_malloc com_conv_init cs_ctx_alloc comn_join_thread ... ct_exit + 0x0299 | |
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 : | 04.02.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) |