DB2 - Problem description
Problem IT19781 | Status: Closed |
IN A DPF DATABASE INSTANCE, IN RARE TIMING CONDITION A SEG-FAULT/TRAP CAN OCCUR IN FUNCTION SQLPSETTID() | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
In a v11.1.1.1 and DPF database instance, in rare timing conditions a seg-fault/trap can occur in function sqlpSetTID(). The stack dump will have a stack similar to this: <StackTrace> -------Frame------ ------Function + Offset------ 0x09000000201857A0 sqlpSetTID__FP8sqeAgentP11SQLP_TENTRYCb + 0x3A0 0x0900000020186088 sqlpGetTEntryForApp__FP8sqeAgentCbPP11SQLP_TENTRY + 0x288 0x09000000201867B0 sqlpsttr__FP8sqeAgent + 0x130 0x0900000020059EAC sqlpAppStart__FP8sqeAgentiPi + 0x22C 0x0900000020072DE8 sqlpWriteNextLsnGapLrecIfRequired__FP14sqlpMasterDbcbP8sqeAgent + 0x568 0x0900000020074AEC sqlpterm__FP16sqeLocalDatabaseP8sqeAgentP5sqlcaCUl + 0x188C 0x090000001F5A224C CleanDB__16sqeLocalDatabaseFbP5sqlca + 0x12AC 0x090000001F59B988 ExecuteDBShutdown__16sqeLocalDatabaseFP8sqeAgentPbP5sqlcai + 0x708 0x090000001F58D2D0 TermDbConnect__16sqeLocalDatabaseFP8sqeAgentP5sqlcai + 0x2B10 0x090000001FC1356C AppStopUsing__14sqeApplicationFP8sqeAgentUcP5sqlca + 0x14EC | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 11.1 Mod1 Fix Pack 1 iFix001 * **************************************************************** | |
Local Fix: | |
Fixed in fixpack inclusive of this APAR fix. | |
available fix packs: | |
DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 11.1 Mod1 Fix Pack 1 iFix001 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 20.03.2017 01.05.2017 01.05.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |