DB2 - Problem description
Problem IT15849 | Status: Closed |
DB2 MAY CRASH IN SQEAGENT::INTERRUPTAGENT DUE TO A TIMING ISSUE | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
1. Problem description DB2 may crash with signal #4 (SIGILL) due to a timing issue in latch 2. Operating system and level: DB2 10.5 fp3 3. Diagnostic information DB2 agent may get signal 4(SIGILL) and the whole DB2 instance will crash. Trap file will have Signal information as below. .............................................. </Siginfo_t> Signal #4 (SIGILL): si_addr is 0x0000000000000000, si_code is 0x0000001E (ILL_ILLOPC:Illegal opcode.) </SignalDetails> .............................................. The call stacks will look like the following: .............................................. sqeAgent::InterruptAgent.fdpr.chunk.6 sqeAgent::InterruptAgent sqeApplication::ExecuteInterrupt.fdpr.chunk.16 .() .() sqlkdInterrupt sqlriecc sqlrr_process_close_request.fdpr.chunk.1 sqlrr_fetch_error sqlrr_open.fdpr.chunk.3 sqljsParseRdbAccessed.fdpr.chunk.187 sqljsSqlam.fdpr.chunk.49 sqljsSqlam.fdpr.chunk.49 sqljsSqlam.fdpr.chunk.49 sqljsDriveRequests sqljsInitAgent.fdpr.chunk.1 sqeAgent::RunEDU.fdpr.chunk.103 sqeAgent::RunEDU.fdpr.chunk.140 sqle_concentrator.sqloRunInstance.fdpr.chunk.25.sqzEDUObj::EDUDr iver sqloEDUEntry .............................................. 4. Local fix N/A | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 10.5 Fix Pack 9 or higher * **************************************************************** | |
Local Fix: | |
Solution | |
First fixed in Db2 10.5 Fix Pack 9 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 24.06.2016 29.09.2017 29.09.2017 |
Problem solved at the following versions (IBM BugInfos) | |
9.0. | |
Problem solved according to the fixlist(s) of the following version(s) |