DB2 - Problem description
Problem IT41547 | Status: Closed |
INSTANCE CRASHED WHEN MULTIPLE CONNECTIONS IMPLICITLY ACTIVATE DATABASE WITH DIFFERENT CODEPAGE SETTING. | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
Instance crashed when multiple user implicity activate database with different code page setting. -------Frame------ ------Function + Offset------ 0x0900000015980A34 sqlpUpdateGlobalTimeInGLFH__FP9sqeBsuEduP16sqeLocalDatabase + 0x244 0x09000000179C4EF8 sqlogctGlobalTerm__FP9sqeBsuEduP16sqeLocalDatabase + 0x108 0x09000000143C419C CleanDB__16sqeLocalDatabaseFbP5sqlca + 0x1ABC 0x09000000143BBC64 ExecuteDBShutdown__16sqeLocalDatabaseFP8sqeAgentPbP5sqlcai + 0x744 0x09000000143A92FC TermDbConnect__16sqeLocalDatabaseFP8sqeAgentP5sqlcai + 0x389C 0x09000000146526D4 HandleStartUsingError__14sqeApplicationFP8sqeAgentP8SQLE_BWAP5sq lcaP22SQLESRSU_STATUS_VECTOR + 0x474 0x090000001463531C AppStartUsing__14sqeApplicationFP8SQLE_BWAP8sqeAgentcT3P5sqlcaPc + 0xA3C 0x0900000014657D28 AppLocalStart__14sqeApplicationFP14db2UCinterface + 0x3BD8 0x090000001475A684 sqlelostWrp__FP14db2UCinterface + 0x44 0x0900000014753A60 sqleUCengnInit__FP14db2UCinterfaceUs + 0xA40 0x0900000014754364 sqleUCagentConnect + 0x734 0x09000000149CC8C0 sqljsConnectAttach__FP13sqljsDrdaAsCbP14db2UCinterface + 0x310 0x09000000149B39F0 sqljs_ddm_accsec__FP14db2UCinterfaceP13sqljDDMObject + 0xD20 0x090000001B6D1868 sqljsParseConnect__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UCinte rface + 0x1D8 0x090000001B6D4D74 sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb + 0x2384 0x090000001B69D588 IPRA.$sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0xC08 0x090000001B6A6AE8 sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xB8 0x090000001B69B6E0 IPRA.$sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x1460 0x090000001B6988FC sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 0x33C 0x090000001392EEC8 RunEDU__8sqeAgentFv + 0xCC8 0x09000000138F26B0 EDUDriver__9sqzEDUObjFv + 0x2F0 0x0900000013806414 sqloEDUEntry + 0x364 to reproduce the issue, we have to satisfy the following conditions at least: 1) the database codepage is 1386, the db2codepage registry variable is 1392 2) do NOT explicitly activate the database, but use a connection to implicitly activate the database 3) multiple connections trying to connect to the database in parallel | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * AIX, Linux, Windows * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * explicitly activate database or upgrade to 11.5.8 * **************************************************************** | |
Local Fix: | |
explicitly ACTIVATE DATABASE | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * AIX, Linux, Windows * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * explicitly activate database or upgrade to 11.5.8 * **************************************************************** | |
Comment | |
Fixed in 11.5.8 | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 18.07.2022 11.08.2022 11.08.2022 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |