|
Problem IC96573
|
Status: Closed |
DB2 CRASHES WHEN THREE PART NAME IS USED ON NON-CATALOG NODE. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
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 " |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* users on DPF instances. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade the database server to v10.5 Fix Pack 3 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
This problem has first been fixed in V10.5 Fix Pack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.10.2013
27.02.2014
27.02.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
