home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT05005 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
Lösung
First fixed in DB2 Version 10.5, Fix pack 7
Workaround
see Local Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
17.10.2014
29.01.2016
29.01.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList