DB2 FOR LUW / DB2FORLUW / A10 - DB2

When a three part name is used from a non-catalog node in a DPF 
configuration, DB2 could crash with following stack: 
 
 
 
sqloEDUCodeTrapHandler 
sqlnq_resolve_systype_name 
sqlrl_create_nickname_cd 
sqlrl_create_nickname_pd 
sqlrlc_fed_fetch_3pn_pd 
sqlrlc_fed_load_entry 
sqlrlc_load_entry 
sqlrlc_request_ulock 
sqlrlc_find_request_usage_lock 
sqlrlc_fetch_router 
sqlrlc_rpc_router 
sqlrr_rpc_router 
sqlrr_subagent_router 
 
For example,  assuming node 0 is the catalog node,  server2 is 
the server object for a remote data source, following command 
could trigger the crash: 
 
export DB2NODE=1 
db2 connect to <db> 
db2 "select count(*) from sysibm.syscolumns c, 
SERVER2.SYSIBM.SYSTABLES t where c.tbname = t.name "

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the database server to V10.1 Fix Pack 3              * 
****************************************************************

DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

This problem was first fixed in DB2 V10.1 Fix Pack 3

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC96573 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

21.08.2013
21.10.2013
21.10.2013