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 IT18653 Status: Closed

PD_GET_DIAG_HIST GOT PANIC OR -902 IN DPF

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
In DPF environment, SQL statements using  PD_GET_DIAG_HIST table 
function failed with SQL0902C or panic. 
 
Example of db2diag.log for the case getting SQL0902C. 
 
2016-12-12-03.37.02.760961-300 I9275882A1683        LEVEL: 
Severe 
PID     : 58982586             TID : 7761           PROC : 
db2sysc 0 
INSTANCE: USER001              NODE : 000           DB   : 
DBNAME1 
APPHDL  : 0-68                 APPID: *N0.USER001.161212083701 
AUTHID  : USER001              HOSTNAME: hostname1 
EDUID   : 7761                 EDUNAME: db2agntp (DBNAME1) 0 
FUNCTION: DB2 UDB, buffer dist serv, sqlkd_rcv_init, probe:11 
DATA #1 : Hexdump, 240 bytes 
0x0000000110973D88 : 0000 0002 0000 0000 0000 0001 FFFF FFFF   
................ 
0x0000000110973D98 : 0000 0000 0000 0000 0000 0000 0000 0000   
................ 
0x0000000110973DA8 : 0000 0000 0000 0000 0000 0000 0000 0000   
................ 
0x0000000110973DB8 : 0000 0000 0000 0000 0000 0000 0000 0000   
................ 
0x0000000110973DC8 : 0000 0000 0000 0000 0000 0000 0000 0000   
................ 
0x0000000110973DD8 : 0780 0000 457D 8080 0780 0000 457D 8118   
....E}......E}.. 
0x0000000110973DE8 : 0780 0000 457D D750 0002 0000 0000 0008   
....E}.P........ 
0x0000000110973DF8 : 0000 0000 0000 0000 0000 0000 0000 0000   
................ 
0x0000000110973E08 : 0000 0000 0000 0000 0000 0000 0000 0000   
................ 
0x0000000110973E18 : 0000 0000 0000 0000 0000 0000 0000 0000   
................ 
0x0000000110973E28 : 0000 0000 0000 0000 0000 0000 0000 0000   
................ 
0x0000000110973E38 : 0000 0000 0000 0000 0000 0000 0000 0000   
................ 
0x0000000110973E48 : 0000 0000 0000 0000 0000 0000 0000 0000   
................ 
0x0000000110973E58 : 0000 0000 0000 0000 0000 0000 0000 0000   
................ 
0x0000000110973E68 : 0000 0000 0000 0000 0000 0000 0000 0000   
................ 
 
2016-12-12-03.37.02.761910-300 I9277566A535         LEVEL: 
Severe 
PID     : 58982586             TID : 7761           PROC : 
db2sysc 0 
INSTANCE: USER001              NODE : 000           DB   : 
DBNAME1 
APPHDL  : 0-68                 APPID: *N0.USER001.161212083701 
AUTHID  : USER001              HOSTNAME: hostname1 
EDUID   : 7761                 EDUNAME: db2agntp (DBNAME1) 0 
FUNCTION: DB2 UDB, buffer dist serv, sqlkd_rcv_init, probe:12 
DATA #1 : Hexdump, 4 bytes 
0x0000000110973D88 : 0000 0002                                 
.... 
 
<snip> &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 
 
2016-12-12-03.37.02.828968-300 I9285525A1054 &#160; &#160; &#160; &#160;LEVEL: 
Severe 
PID &#160; &#160; : 58982586 &#160; &#160; &#160; &#160; &#160; &#160; TID : 7761 &#160; &#160; &#160; &#160; &#160; PROC : 
db2sysc 0 
INSTANCE: USER001 &#160; &#160; &#160; &#160; &#160; &#160; &#160;NODE : 000 &#160; &#160; &#160; &#160; &#160; DB &#160; : 
DBNAME1 
APPHDL &#160;: 0-68 &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; APPID: *N0.USER001.161212083701 
AUTHID &#160;: USER001 &#160; &#160; &#160; &#160; &#160; &#160; &#160;HOSTNAME: hostname1 
EDUID &#160; : 7761 &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; EDUNAME: db2agntp (DBNAME1) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_sibling, 
probe:140 
MESSAGE : section stmt 
DATA #1 : Hexdump, 101 bytes 
0x070000008C38B380 : 696E 7365 7274 2069 6E74 6F20 452E 5443 &#160; 
insert into E.TC 
0x070000008C38B390 : 534D 3032 3554 4553 5420 7365 6C65 6374 &#160; 
SM025TEST select 
0x070000008C38B3A0 : 206D 656D 6265 7220 6672 6F6D 2054 4142 &#160; &#160; 
member from TAB 
0x070000008C38B3B0 : 4C45 2850 445F 4745 545F 4449 4147 5F48 &#160; 
LE(PD_GET_DIAG_H 
0x070000008C38B3C0 : 4953 5428 2741 4C4C 272C 2741 4C4C 272C &#160; 
IST('ALL','ALL', 
0x070000008C38B3D0 : 6E75 6C6C 2C6E 756C 6C2C 6E75 6C6C 2C2D &#160; 
null,null,null,- 
0x070000008C38B3E0 : 3229 2920 74 &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 
2)) t 
 
2016-12-12-03.37.02.830483-300 I9286580A662 &#160; &#160; &#160; &#160; LEVEL: 
Severe 
PID &#160; &#160; : 58982586 &#160; &#160; &#160; &#160; &#160; &#160; TID : 7761 &#160; &#160; &#160; &#160; &#160; PROC : 
db2sysc 0 
INSTANCE: USER001 &#160; &#160; &#160; &#160; &#160; &#160; &#160;NODE : 000 &#160; &#160; &#160; &#160; &#160; DB &#160; : 
DBNAME1 
APPHDL &#160;: 0-68 &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; APPID: *N0.USER001.161212083701 
AUTHID &#160;: USER001 &#160; &#160; &#160; &#160; &#160; &#160; &#160;HOSTNAME: hostname1 
EDUID &#160; : 7761 &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; EDUNAME: db2agntp (DBNAME1) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_section, 
probe:25 
MESSAGE : MASTER TIME INFO 
DATA #1 : Hexdump, 32 bytes 
0x07000000549E9168 : 0000 0000 584E 61A3 032F 0000 000C 71CA &#160; 
....XNa../....q. 
0x07000000549E9178 : 0021 1D03 B319 531F 0000 0000 001F 4000 &#160; 
.!....S.......@. 
 
<snip> 
 
2016-12-12-03.37.02.867890-300 I9291556A541 &#160; &#160; &#160; &#160; LEVEL: 
Severe 
PID &#160; &#160; : 58982586 &#160; &#160; &#160; &#160; &#160; &#160; TID : 7761 &#160; &#160; &#160; &#160; &#160; PROC : 
db2sysc 0 
INSTANCE: USER001 &#160; &#160; &#160; &#160; &#160; &#160; &#160;NODE : 000 &#160; &#160; &#160; &#160; &#160; DB &#160; : 
DBNAME1 
APPHDL &#160;: 0-68 &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; APPID: *N0.USER001.161212083701 
AUTHID &#160;: USER001 &#160; &#160; &#160; &#160; &#160; &#160; &#160;HOSTNAME: hostname1 
EDUID &#160; : 7761 &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; EDUNAME: db2agntp (DBNAME1) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_signal_handler, 
probe:350 
MESSAGE : DIA0506I Execution of a component signal handling 
function is 
&#160; &#160; &#160; &#160; &#160; complete. 
 
2016-12-12-03.37.02.871748-300 E9292098A812 &#160; &#160; &#160; &#160; LEVEL: Error 
PID &#160; &#160; : 58982586 &#160; &#160; &#160; &#160; &#160; &#160; TID : 7761 &#160; &#160; &#160; &#160; &#160; PROC : 
db2sysc 0 
INSTANCE: USER001 &#160; &#160; &#160; &#160; &#160; &#160; &#160;NODE : 000 &#160; &#160; &#160; &#160; &#160; DB &#160; : 
DBNAME1 
APPHDL &#160;: 0-68 &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; APPID: *N0.USER001.161212083701 
AUTHID &#160;: USER001 &#160; &#160; &#160; &#160; &#160; &#160; &#160;HOSTNAME: hostname1 
EDUID &#160; : 7761 &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; EDUNAME: db2agntp (DBNAME1) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:30 
MESSAGE : ADM14005E &#160;The following error occurred: "AppErr". 
First Occurrence 
&#160; &#160; &#160; &#160; &#160; Data Capture (FODC) has been invoked in the following 
mode: 
&#160; &#160; &#160; &#160; &#160; "Automatic". &#160;Diagnostic information has been recorded 
in the 
&#160; &#160; &#160; &#160; &#160; directory named 
&#160; &#160; &#160; &#160; &#160; 
"/home/USER001/sqllib/db2dump/DIAG0000/FODC_AppErr_2016-12-12-03 
.37.0 
&#160; &#160; &#160; &#160; &#160; 2.870615_58982586_7761_000/". 
 
2016-12-12-03.37.02.872813-300 E9292911A586 &#160; &#160; &#160; &#160; LEVEL: 
Severe 
PID &#160; &#160; : 58982586 &#160; &#160; &#160; &#160; &#160; &#160; TID : 7761 &#160; &#160; &#160; &#160; &#160; PROC : 
db2sysc 0 
INSTANCE: USER001 &#160; &#160; &#160; &#160; &#160; &#160; &#160;NODE : 000 &#160; &#160; &#160; &#160; &#160; DB &#160; : 
DBNAME1 
APPHDL &#160;: 0-68 &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; APPID: *N0.USER001.161212083701 
AUTHID &#160;: USER001 &#160; &#160; &#160; &#160; &#160; &#160; &#160;HOSTNAME: hostname1 
EDUID &#160; : 7761 &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; EDUNAME: db2agntp (DBNAME1) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:200 
MESSAGE : ADM0001C &#160;A severe error has occurred. &#160;Examine the 
administration 
&#160; &#160; &#160; &#160; &#160; notification log and contact IBM Support if necessary. 
 
2016-12-12-03.37.02.873782-300 I9293498A1014 &#160; &#160; &#160; &#160;LEVEL: 
Severe 
PID &#160; &#160; : 58982586 &#160; &#160; &#160; &#160; &#160; &#160; TID : 7761 &#160; &#160; &#160; &#160; &#160; PROC : 
db2sysc 0 
INSTANCE: USER001 &#160; &#160; &#160; &#160; &#160; &#160; &#160;NODE : 000 &#160; &#160; &#160; &#160; &#160; DB &#160; : 
DBNAME1 
APPHDL &#160;: 0-68 &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; APPID: *N0.USER001.161212083701 
AUTHID &#160;: USER001 &#160; &#160; &#160; &#160; &#160; &#160; &#160;HOSTNAME: hostname1 
EDUID &#160; : 7761 &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; EDUNAME: db2agntp (DBNAME1) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:250 
MESSAGE : ZRC=0x87580088=-2024275832=SQLKD_COMM_ERR 
&#160; &#160; &#160; &#160; &#160; "BDS internal communication error due to coding error 
and/or corrupted buffer contents" 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
sqlcaid : SQLCA &#160; &#160; sqlcabc: 136 &#160; sqlcode: -902 &#160; sqlerrml: 3 
sqlerrmc: 136 
sqlerrp : SQLRR06D 
sqlerrd : (1) 0x87580088 &#160; &#160; &#160;(2) 0x00000088 &#160; &#160; &#160;(3) 0x00000000 
&#160; &#160; &#160; &#160; &#160; &#160;(4) 0x00000000 &#160; &#160; &#160;(5) 0xFFFFFB50 &#160; &#160; &#160;(6) 
0x00000000 
sqlwarn : (1) &#160; &#160; &#160;(2) &#160; &#160; &#160;(3) &#160; &#160; &#160;(4) &#160; &#160; &#160; &#160;(5) &#160; &#160; &#160; (6) 
&#160; &#160; &#160; &#160; &#160; &#160;(7) &#160; &#160; &#160;(8) &#160; &#160; &#160;(9) &#160; &#160; &#160;(10) &#160; &#160; &#160; &#160;(11) 
sqlstate: 
 
Example of stack traces for the case of failure in panic. 
 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x0900000000125F9C thread_wait + 0x9C 
0x090000000EA99CC0 sqloWaitEDUWaitPost + 0xA00 
0x090000000ECC5020 WaitRecvReady__11sqkfChannelFiT1 + 0x1260 
0x090000000ECD5050 ReceiveBuffer__11sqkfChannelFPP10sqkfBufferi 
+ 0xDD0 
0x090000000F663854 
getNextBuffer__18sqkdBdsBufferTableFPP10sqkfBufferP8SQLKD_CB + 
0x13B4 
0x090000000F661F94 sqlkd_rcv_buffer__FP8SQLKD_CBPP10sqkfBuffer + 
0x54 
0x090000000F658CD4 IPRA.$sqlkd_rcv_get_next_buffer__FP8SQLKD_CB 
+ 0x54 
0x090000000F65A9C0 sqlkd_rcv_init__FP8SQLKD_CBiN22 + 0x240 
0x090000000F65BD1C 
sqlkdReceiveReply__FP23SQLKD_RQST_REPLY_FORMAT + 0x89C 
0x090000000F691C18 
sqleReceiveAndMergeReplies__FP24SQLE_RECEIVE_MERGE_INPUTP25SQLE_ 
RECEIVE_MERGE_OUTPUTP5sqlcaP8sqlrr_cb + 0x918 
0x090000000F62D5A0 
sqlkdInterrupt__FP22SQLKD_INTERRUPT_FORMATP5sqlcaP8sqlrr_cb + 
0xFA0 
0x0900000011ADD14C 
sqlrr_coor_rbsvpt__FP8sqlrr_cbiP19sqlr_savepoint_infoT2 + 0xCCC 
0x0900000011AEBA80 
sqlr_rollback_savept__FP8sqlrr_cbiUiP19sqlr_savepoint_infoT2 + 
0x1220 
0x09000000127D2EF4 
sqlrices__FP8sqlrr_cbP25sqlra_sql_context_siblingi + 0x154 
0x090000000F8D5780 sqlriCloseExecuteSectionComplex__FP8sqlrr_cbi 
+ 0x6A0 
0x09000000127C96E8 sqlrr_execute_immediate__FP8sqlrr_cbi + 
0x2588 
0x090000001424625C 
sqlrr_execimmd__FP14db2UCinterfaceP16db2UCprepareInfo + 0x87C 
0x090000001567FAE0 
sqljs_ddm_excsqlimm__FP14db2UCinterfaceP13sqljDDMObject + 0x1220 
0x09000000155FC3C8 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface + 0x268 
0x09000000155FF450 
sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb + 
0x2250 
0x09000000155CFDE4 
IPRA.$sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x964 
0x09000000155D89B4 
sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xB4 
0x09000000155CE3D0 
IPRA.$sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x13D0 
0x09000000155CB834 sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 
0x334 
0x090000000EAB23E0 RunEDU__8sqeAgentFv + 0xB40 
0x090000000EA95CA0 EDUDriver__9sqzEDUObjFv + 0x2E0 
0x090000000E98A694 sqloEDUEntry + 0x374 
</StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher               * 
****************************************************************
Local Fix:
If you use $m in DIAGPATH, please do not use $m in DIAGPATH. 
It may avoid this problem.
available fix packs:
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
Solution
First fixed in DB2 11.1 Mod 2 Fix Pack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

04.01.2017
23.06.2017
23.06.2017
Problem solved at the following versions (IBM BugInfos)


Problem solved according to the fixlist(s) of the following version(s)