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

DB2 MIGHT ABEND WHILE MATCHING OPTIMIZER MQT FOR QUERY WITH MORE THAN 30
JOINS

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Under rare scenarios, DB2 might abend for a query which 
satisfies the following conditions: 
1. The query has more than 30 inner joins 
2. There are one or more optimizer mqts defined on the tables. 
 
<Stack Trace> 
-----FUNC-ADDR---- ------FUNCTION + OFFSET------ 
sqlnq_mch::find_qun_mappings 
sqlnr_subsume_derived_match 
sqlnr_subsume_match 
sqlnr_matchmaker 
sqlnr_compute_matchinfo 
sqlnr_optprep 
sqlnr_optprep_action 
sqlnr_comp 
sqlnr_seq 
sqlnr_rcc 
sqlnr_exe 
sqlnn_cmpl 
</StackTrace> 
 
The following messages will be written to the db2diag.log 
 
2011-08-22-10.53.35.331275-240 I183347E496         LEVEL: Event 
PID     : 17926                TID  : 183135889760 PROC : 
db2sysc 0 
INSTANCE: nypit076             NODE : 000          DB   : EMPDB 
APPHDL  : 0-13                 APPID: *LOCAL.DB2.110821094136 
AUTHID  : MSDB2 
EDUID   : 66                   EDUNAME: db2stmm (EMPDB) 0 
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, 
probe:20 
CHANGE  : STMM CFG DB EMPDB: "Pckcachesz" From: "12161" 
<automatic>  To: "12321" <automatic> 
 
2011-08-22-10.54.37.596076-240 I183844E618         LEVEL: Error 
PID     : 17926                TID  : 207597070688 PROC : 
db2sysc 0 
INSTANCE: nypit076             NODE : 000          DB   : EMPDB 
APPHDL  : 0-6242               APPID: 
10.184.103.47.6084.110822141846 
AUTHID  : PHST1933 
EDUID   : 233                  EDUNAME: db2agent (EMPDB) 0 
FUNCTION: DB2 UDB, access plan manager, sqlra_intd_call, 
probe:200 
MESSAGE : Out sqlz_value 
DATA #1 : Hexdump, 24 bytes 
0x0000002F56FF8DA8 : 1301 4000 0108 0000 A006 0000 0000 0000 
..@............. 
0x0000002F56FF8DB8 : 4000 0000 0000 0000 
@....... 
 
2011-08-22-10.54.37.596289-240 I184463E618         LEVEL: Error 
PID     : 17926                TID  : 207597070688 PROC : 
db2sysc 0 
INSTANCE: nypit076             NODE : 000          DB   : EMPDB 
APPHDL  : 0-6242               APPID: 
10.184.103.47.6084.110822141846 
AUTHID  : PHST1933 
EDUID   : 233                  EDUNAME: db2agent (EMPDB) 0 
FUNCTION: DB2 UDB, access plan manager, sqlra_intd_call, 
probe:200 
MESSAGE : Out sqlz_value 
DATA #1 : Hexdump, 24 bytes 
0x0000002F56FF8CA8 : 1301 4000 0108 0000 A005 0000 0000 0000 
..@............. 
0x0000002F56FF8CB8 : 4000 0000 0000 0000 
@....... 
 
2011-08-22-10.54.37.596374-240 I185082E618         LEVEL: Error 
PID     : 17926                TID  : 207597070688 PROC : 
db2sysc 0 
INSTANCE: nypit076             NODE : 000          DB   : EMPDB 
APPHDL  : 0-6242               APPID: 
10.184.103.47.6084.110822141846 
AUTHID  : PHST1933 
EDUID   : 233                  EDUNAME: db2agent (EMPDB) 0 
FUNCTION: DB2 UDB, access plan manager, sqlra_intd_call, 
probe:200 
MESSAGE : Out sqlz_value 
DATA #1 : Hexdump, 24 bytes 
0x0000002F56FF8BA8 : 1301 4000 0108 B804 A004 0000 0000 0000 
..@............. 
0x0000002F56FF8BB8 : 4000 0000 0000 0000 
@....... 
 
2011-08-22-11.38.42.370399-240 I185701E567         LEVEL: Error 
PID     : 17926                TID  : 208133941600 PROC : 
db2sysc 0 
INSTANCE: nypit076             NODE : 000          DB   : EMPDB 
APPHDL  : 0-6426               APPID: 
172.23.255.60.56837.11082215383 
AUTHID  : RFZHOU 
EDUID   : 140                  EDUNAME: db2agent (EMPDB) 0 
FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh, 
probe:1 
MESSAGE : Error in agent servicing application with coor_node: 
DATA #1 : Hexdump, 2 bytes 
0x000000307580F592 : 0000
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 version 970 fixpack 6                  * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem is fixed in DB2 version 970 fixpack 6
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.10.2011
06.06.2012
06.06.2012
Problem solved at the following versions (IBM BugInfos)
9.7.0
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.