Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT09317 Status: Geschlossen

CRASH WITH SIGNAL#8 WHEN RUNNING EXPLAIN COMMAND

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
Running the explain command can crash the instance and below 
information may be recorded in db2diag.log: 
 
======================== 
2015-05-07-09.15.56.024590-180 I101929167A2677      LEVEL: 
Severe 
PID     : 18019                TID : 4394426820880  PROC : 
db2sysc 0 
INSTANCE: xxxxxxxx             NODE : xxxx           DB   : xxxx 
APPHDL  : 0-59799              APPID: xxxxx 
AUTHID  : xxxxxxxx             HOSTNAME: xxxxxxx 
EDUID   : 43788                EDUNAME: db2agent (AUD_TBP) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_sibling, 
probe:200 
MESSAGE : section stmt 
DATA #1 : Hexdump, 419 bytes 
0x000003FFBD8F1280 : 4558 504C 4149 4E20 504C 414E 2073 656C 
EXPLAIN PLAN command 
 
 
2015-05-07-09.15.53.651342-180 I101902134A394       LEVEL: Event 
PID     : 2162                 TID : 4397832025872  PROC : db2pd 
INSTANCE: xxxxxxx              NODE : xxxx 
HOSTNAME: xxxxxxxx 
FUNCTION: DB2 UDB, RAS/PD component, pdGetDumpFileDescriptor, 
probe:20 
START   : Check 
/xxx/xxxx/xxxxxxx/fodc/FODC_Trap_2015-05-07-09.15.49.500064_0000 
/db2pd.dpsdbcb.AUD_TBP.txt for additional data. 
 
2015-05-07-09.16.01.754355-180 E101978287A590       LEVEL: 
Severe 
PID     : 18017                TID : 4397568354576  PROC : 
db2wdog 0[xxxxx] 
INSTANCE: xxxxxxx              NODE : xxxxxx 
HOSTNAME: xxxxxxxx 
EDUID   : 2                    EDUNAME: db2wdog 0 [xxxxxxxx] 
FUNCTION: DB2 UDB, base sys utilities, sqleWatchDog, probe:20 
MESSAGE : ADM0503C  An unexpected internal processing error has 
occurred. All 
          DB2 processes associated with this instance have been 
shutdown. 
          Diagnostic information has been recorded. Contact IBM 
Support for 
          further assistance. 
 
2015-05-07-09.16.01.754355-180 E101978287A590       LEVEL: 
Severe 
PID     : 18017                TID : 4397568354576  PROC : 
db2wdog 0[xxxxxxx] 
INSTANCE: xxxxxxxx             NODE : xxxxxx 
HOSTNAME: xxxxxxxx 
EDUID   : 2                    EDUNAME: db2wdog 0 [xxxxxxx] 
FUNCTION: DB2 UDB, base sys utilities, sqleWatchDog, probe:20 
MESSAGE : ADM0503C  An unexpected internal processing error has 
occurred. All 
          DB2 processes associated with this instance have been 
shutdown. 
          Diagnostic information has been recorded. Contact IBM 
Support for further assistance. 
 
2015-05-07-09.16.02.411524-180 E101978878A466       LEVEL: Error 
PID     : 18017                TID : 4397568354576  PROC : 
db2wdog 0[xxxxxxxx] 
INSTANCE: xxxxxxxx             NODE : xxxx 
HOSTNAME: xxxxxxxxx 
EDUID   : 2                    EDUNAME: db2wdog 0 [xxxxxxx] 
FUNCTION: DB2 UDB, base sys utilities, sqleWatchDog, probe:8178 
DATA #1 : Process ID, 4 bytes 
18019 
DATA #2 : Hexdump, 8 bytes 
0x000003FFE37FD794 : 0000 0101 0000 0008       ->> SIGFPE   8 
Floating point exception (ANSI) 
 
 
Stack generated: 
======================== 
 
_Z25ossDumpStackTraceInternalmR11OSSTrapFileiP7siginfoPvm 
OssDumpStackTraceV98 
_ZN11OSSTrapFile4dumpEmiP7siginfoPv 
sqlo_trce 
sqloEDUCodeTrapHandler 
_Z20sqlno_hash_calc_stmtPhji 
_Z27sqlno_optprofile_find_matchP28sqlno_optprofile_stmtprofileP1 
6sqlno_optprofilePS0 
_Z25sqlno_hint_get_optprofileP3loc15sqlno_oprof_cxtPP16sqlno_opt 
profilePP28sqlno_optprofile_stmtprofileS4_P12sqlnq_string 
_Z19sqlnnProcessProfileP12sqlnq_stringP3loc 
_Z10sqlnp_mainP12sqlnq_stringbP3locPP9sqlnq_qur 
_Z10sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sq 
lrr_cmpl_enviiPP9sqlnq_qur 
_Z10sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sq 
lrr_cmpl_env 
_Z17sqlra_compile_varP8sqlrr_cbP14sqlra_cmpl_envPhitiiiiiP14SQLP 
_LOCK_INFOP16sqlra_cached_varPi 
_Z14sqlra_find_varP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idj 
jPhjthP14sqlra_cmpl_env15sqlra_fill_modePiiS8_iiiS8_P14SQLP_LOCK 
_INFOPP16sqlra_cached_varS8_b 
_Z28sqlra_statement_concentratorP8sqlrr_cbP10sqlr_cacheP17sqlra_ 
cached_stmt13sqlra_stmt_idtjPhjthP14sqlra_cmpl_envPiiS9_iiiS9_P1 
4SQLP_LOCK_INFOPP16sqlra_cached_varS9_b 
_Z13sqlra_get_varP8sqlrr_cbiibPbS1 
_Z23sqlrr_execute_immediateP8sqlrr_cbi 
_Z14sqlrr_execimmdP14db2UCinterfaceP16db2UCprepareInfo 
_Z19sqljs_ddm_excsqlimmP14db2UCinterfaceP13sqljDDMObject 
_Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2U 
Cinterface 
_Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb 
_Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T 
_ZN8sqeAgent6RunEDUEv 
_ZN9sqzEDUObj9EDUDriverEv 
sqloEDUEntry
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See problem description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version V10.5 Fix Pack 7.                     * 
****************************************************************
Local-Fix:
Avoid running explain command.
Lösung
First fixed in Version V10.5 Fix Pack 7.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
05.06.2015
25.11.2015
25.11.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList