home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT04519 Status: Closed

SQKFCHANNEL::WAITSENDREADY RECIEVES SQLO_INTRP INTERRUPT AND RESULTS IN
PANIC

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
You may experience a crash on nodes in a DPF environment which 
may result in the following diaglog entry with the following 
reason code associated with it: 
 
014-03-13-02.07.47.078766-300 I68635335E582         LEVEL: 
Severe 
PID     : 30052                TID : 46952683136768  PROC : 
db2sysc 69 
INSTANCE: myinst1             NODE : 069            DB   : mydb1 
APPHDL  :            APPID: 
AUTHID  :              HOSTNAME: 
EDUID   : 152528               EDUNAME: db2agntp 69 
FUNCTION: DB2 UDB, fast comm manager, 
sqkfChannel::isAnySendReady, probe:10 
MESSAGE : Unexpected error: rc = 
DATA #1 : Hexdump, 4 bytes 
0x00002AB405FFCE98 : 0300 0F80 
.... 
[. . .] 
2014-03-13-02.09.36.412359-300 I72632727E1881        LEVEL: 
Severe 
PID     : 30052                TID : 46952683136768  PROC : 
db2sysc 69 
INSTANCE: myinst1             NODE : 069            DB   : mydb1 
APPHDL  :            APPID: 
AUTHID  :             HOSTNAME: 
EDUID   : 152528               EDUNAME: db2agntp 69 
FUNCTION: DB2 UDB, base sys utilities, sqle_panic, probe:10 
DATA #1 : <preformatted> 
sqle_panic: Panic/sleep = 0x0 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
  [0] 0x00002AAAABC1B804 pdLogVPrintf + 0x2D4 
  [1] 0x00002AAAABC1B51C pdLogPrintf + 0x8C 
  [2] 0x00002AAAAD685B63 _Z10sqle_panicv + 0x1E3 
  [3] 0x00002AAAAD83FAEF _ZN11sqkfChannel14isAnySendReadyEPhiiPi 
+ 0x2CF 
  [4] 0x00002AAAAC1B6DBC 
_Z8sqlkqsndP8SQLKQ_CBP8sqeAgentiPP10sqkfBufferit + 0x78C 
  [5] 0x00002AAAAC1BD0EA _Z8sqlktsndP9sqlri_taoit + 0x11A 
  [6] 0x00002AAAAEDF22A0 
_Z16sqlkt_pack_tupleP10SQLD_FIELDP9sqlri_taolPP10SQLD_VALUEP5sql 
catP8sqeAgent + 0x1F0 
  [7] 0x00002AAAAEDF133C 
_Z8sqlktinsP7sqlr_dbP8sqeAgentP10sqlri_iudoP5sqlcat + 0x23C 
  [8] 0x00002AAAAE599CCC _Z8sqlritqbP8sqlrr_cb + 0x51C 
  [9] 0x00002AAAAEF542BD 
_Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm + 0x1AD 
  [10] 0x00002AAAAE303DCD _Z16sqlrr_dss_routerP8sqlrr_cb + 0x6CD 
  [11] 0x00002AAAACAA940E 
_Z21sqlrr_subagent_routerP8sqeAgentP12SQLE_DB2RA_T + 0x4BE 
  [12] 0x00002AAAABEDFB52 
/home/db2admn/sqllib/lib64/libdb2e.so.1 + 0x1217B52 
  [13] 0x00002AAAABEDEDB3 _Z21sqleProcessSubRequestP8sqeAgent + 
0xE3 
  [14] 0x00002AAAABEF94B4 _ZN8sqeAgent6RunEDUEv + 0x604 
  [15] 0x00002AAAACEE2543 _ZN9sqzEDUObj9EDUDriverEv + 0xF3 
  [16] 0x00002AAAACEE2449 _Z10sqlzRunEDUPcj + 0x9 
  [17] 0x00002AAAAC96C541 sqloEDUEntry + 0x2A1 
  [18] 0x000000359C607851 /lib64/libpthread.so.0 + 0x7851 
  [19] 0x000000359C2E894D clone + 0x6D 
 
 
The stack trace should be following with the signal # 12: 
 
<StackTrace> 
0x00002AAAB2523DDA 
_Z25ossDumpStackTraceInternalmR11OSSTrapFileiP7siginfoPvmm + 
0x020a 
0x00002AAAB2523B6B ossDumpStackTraceV98 + 0x002b 
0x00002AAAB251EA93 _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 
0x0103 
0x00002AAAAE06E687 sqlo_trce + 0x0407 
0x00002AAAAE0BA434 sqloDumpDiagInfoHandler + 0x0104 
0x000000359C60F500 address: 0x000000359C60F500 ; dladdress: 
0x000000359C600000 ; offset in lib: 0x000000000000F500 ; 
0x000000359C60C69C pthread_kill + 0x002c 
0x00002AAAAC96E6AB _Z14ossPthreadKillmj + 0x000b 
0x00002AAAAE0BA737 sqloDumpEDU + 0x0047 
0x00002AAAAD685A53 _Z10sqle_panicv + 0x00d3 
0x00002AAAAD83FAEF _ZN11sqkfChannel14isAnySendReadyEPhiiPi + 
0x02cf 
0x00002AAAAC1B6DBC 
_Z8sqlkqsndP8SQLKQ_CBP8sqeAgentiPP10sqkfBufferit + 0x078c 
0x00002AAAAC1BD0EA _Z8sqlktsndP9sqlri_taoit + 0x011a 
0x00002AAAAEDF22A0 
_Z16sqlkt_pack_tupleP10SQLD_FIELDP9sqlri_taolPP10SQLD_VALUEP5sql 
catP8sqeAgent + 0x01f0 
0x00002AAAAEDF133C 
_Z8sqlktinsP7sqlr_dbP8sqeAgentP10sqlri_iudoP5sqlcat + 0x023c 
0x00002AAAAE599CCC _Z8sqlritqbP8sqlrr_cb + 0x051c 
0x00002AAAAEF542BD _Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm 
+ 0x01ad 
0x00002AAAAE303DCD _Z16sqlrr_dss_routerP8sqlrr_cb + 0x06cd 
0x00002AAAACAA940E 
_Z21sqlrr_subagent_routerP8sqeAgentP12SQLE_DB2RA_T + 0x04be 
0x00002AAAABEDFB52 address: 0x00002AAAABEDFB52 ; dladdress: 
0x00002AAAAACC8000 ; offset in lib: 0x0000000001217B52 ; 
0x00002AAAABEDEDB3 _Z21sqleProcessSubRequestP8sqeAgent + 0x00e3 
0x00002AAAABEF94B4 _ZN8sqeAgent6RunEDUEv + 0x0604 
0x00002AAAACEE2543 _ZN9sqzEDUObj9EDUDriverEv + 0x00f3 
0x00002AAAACEE2449 _Z10sqlzRunEDUPcj + 0x0009 
0x00002AAAAC96C541 sqloEDUEntry + 0x02a1 
0x000000359C607851 address: 0x000000359C607851 ; dladdress: 
0x000000359C600000 ; offset in lib: 0x0000000000007851 ; 
0x000000359C2E894D clone + 0x006d 
</StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 5.                      * 
****************************************************************
Local Fix:
Solution
First fixed in Version 10.5 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.09.2014
31.03.2015
31.03.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.5 FixList