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

FEDERATED SERVER CAN CRASH WHEN SQLNN_ADJUST_LIST CALLS MEMCPY AND USING
3-PART NAME

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
When trying to query a federated database using a 3-part name, 
the DB2 instance can crash. 
 
The trap file can contain the following series of functions in 
its stack trace: 
 
memcpy 
sqlnn_adjust_list 
sqlnn_authdep_list 
sqlnn_authdep_list 
sqlnn_authdep_list 
sqlnn_authdep_list 
sqlnn_cmpl 
sqlnn_cmpl 
sqlra_compile_var 
sqlra_find_var 
sqlra_get_var 
sqlrr_prepare 
sqljs_ddm_prpsqlstt 
sqljsParseRdbAccessed 
sqljsParse 
sqljsSetupDrdaAsForApp 
sqljsSetupDrdaAsForApp 
sqljsDrdaAsDriver 
sqljsDrdaAsDriver 
sqeAgentGRunEDU 
sqzEDUObjJEDUDriver 
sqloEDUEntry 
 
This problem is more likely to occur on the Solaris platform.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5, Fix pack 7                      * 
****************************************************************
Local Fix:
Create a nickname, and then query using the nickname as opposed 
to using a 3-part name.
Solution
First fixed in DB2 Version 10.5, Fix pack 7
Workaround
see Local Fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.10.2014
29.01.2016
29.01.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList