DB2 - Problembeschreibung
Problem IC99233 | Status: Geschlossen |
DB2 INSTANCE MAY TRAP WITH SIGNAL#11 WITH FUNCTION SQLNX_EXP_DUMP_DIAG_CACHE. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
db2 instance may trap with Signal#11 with the function call sqlnx_exp_dump_diag_cache when the underlying SQL statement involving MQTs are very long. The stack trace will be as follows: <StackTrace> -----FUNC-ADDR---- ------FUNCTION + OFFSET------ 0x00002AAAB2743DBA￴ _Z25ossDumpStackTraceInternalmR11OSSTrapFileiP7siginfoPvmm + 0x020a (/var/ibmdb2/nypit053/sqllib/lib64/libdb2osse.so.1) 0x00002AAAB2743B4B ossDumpStackTraceV98 + 0x002b (/var/ibmdb2/nypit053/sqllib/lib64/libdb2osse.so.1) 0x00002AAAB273EA73 _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 0x0103 (/var/ibmdb2/nypit053/sqllib/lib64/libdb2osse.so.1) 0x00002AAAAE288BF7 sqlo_trce + 0x0407 (/var/ibmdb2/nypit053/sqllib/lib64/libdb2e.so.1) 0x00002AAAAE2D3DE7 sqloEDUCodeTrapHandler + 0x0277 (/var/ibmdb2/nypit053/sqllib/lib64/libdb2e.so.1) 0x00002AAAAACD7CA0 address: 0x00002AAAAACD7CA0 ; dladdress:￴ 0x00002AAAAACC9000 ; offset in lib: 0x000000000000ECA0 ; (/lib64/libpthread.so.0) 0x0000000000426377 __intel_ssse3_rep_memcpy + 0x1fa7 (db2sysc 0) 0x000000000041DA56 _intel_fast_memcpy.P + 0x0006 (db2sysc 0) 0x00002AAAACAD02AF _Z25sqlnx_exp_dump_diag_cacheP14sqlnx_exp_data +￴ 0x026f (/var/ibmdb2/nypit053/sqllib/lib64/libdb2e.so.1) 0x00002AAAACACF993 _Z18sqlnx_explain_planP9sqlnq_qur + 0x0583 0x00002AAAAC50BAF9 _Z10sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sq lrr_cmpl_enviiP P9sqlnq_qur + 0x40c9 (/var/ibmdb2/nypit053/sqllib/lib64/libdb2e.so.1) 0x00002AAAAC507A21 _Z10sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sq lrr_cmpl_env + 0x0021 (/var/ibmdb2/nypit053/sqllib/lib64/libdb2e.so.1) 0x00002AAAACD1FA90 _Z17sqlra_compile_varP8sqlrr_cbP14sqlra_cmpl_envPhitiiiiiP14SQLP _LOCK_INFOP16sq lra_cached_varPi + 0x0820 (/var/ibmdb2/nypit053/sqllib/lib64/libdb2e.so.1) 0x00002AAAACD2D92A _Z14sqlra_find_varP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idj jPhjthP14sqlra_ cmpl_env15sqlra_fill_modePiiS8_iiiS8_P14SQLP_LOCK_INFOPP16sqlra_ cached_varS8_b + 0x065a (/var/ibmdb2/nypit053/sqllib/lib64/libdb2e.so.1) 0x00002AAAACD68D96 _Z13sqlra_get_varP8sqlrr_cbiibPbS1_ + 0x0876 (/var/ibmdb2/nypit053/sqllib/lib64/libdb2e.so.1) 0x00002AAAACCB0758 _Z13sqlrr_prepareP14db2UCinterfaceP16db2UCprepareInfo + 0x0388 (/var/ibmdb2/nypit053/sqllib/lib64/libdb2e.so.1) | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * DB2 LUW using explain, and having MQTs or Statviews with * * definitions > 16k of text. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Customers experiencing this issue should upgrade to DB2 * * Cancun Release 10.5.0.4 or higher. * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Lösung | |
DB2 Cancun Release 10.5.0.4 and higher contain this fix. The fix causes the full Explain Diagnostic text to be recorded in the explain_diagnostic tables. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 07.02.2014 06.10.2014 06.10.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.4 |