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 IC86577 Status: Geschlossen

INSTANCE CRASH WHEN USING ASSOCIATIVE ARRAY OF VARIABLE LENGTH

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
DB2 may crash when invoking a stored procedure that contains a 
variable that is mapped to an associative array of variable 
length. 
 
The call stack that gets generated from the DB2 trap file will 
be as follows: 
 
<associativeArrayHeader::cloneHelper> 
<T:\db2_galileo\ntx64\s120403\engn\sqri\sqlriArray.C:6564> 
<associativeArrayHeader::cloneAssocArrayHdr> 
<T:\db2_galileo\ntx64\s120403\engn\include\sqlriArray.h:585> 
<sqlriArrayDescriptor::cloneDyn> 
<T:\db2_galileo\ntx64\s120403\engn\sqri\sqlriArray.C:1564> 
<sqlriArrayDescriptor::copy> 
<T:\db2_galileo\ntx64\s120403\engn\sqri\sqlriArray.C:1878> 
<sqlrxArrayCopy> 
<T:\db2_galileo\ntx64\s120403\engn\sqv\sqlrxArray.C:71> 
<sqlriSetupGlobalVariablesInSection> 
<T:\db2_galileo\ntx64\s120403\engn\sqri\sqlriSectInit.C:7996> 
<sqlriInitializeGlobalVariables> 
<T:\db2_galileo\ntx64\s120403\engn\sqri\sqlri_misc.C:8264> 
<sqlriSectInvoke> 
<T:\db2_galileo\ntx64\s120403\engn\include\sqlriManageSections.h 
:1582> 
<sqlrr_process_execute_request> 
<T:\db2_galileo\ntx64\s120403\engn\include\sqlriManageSections.h 
:1329> 
<sqlrr_execute> 
<T:\db2_galileo\ntx64\s120403\engn\sqr\sqlrr_req_sql.C:848> 
<pvmPackage::executeSection> 
<T:\db2_galileo\ntx64\s120403\engn\psm\psm_pvm.C:2991> 
<PVM::run> 
<T:\db2_galileo\ntx64\s120403\engn\psm\psm_pvm.C:6004> 
<pvm_entry> 
<T:\db2_galileo\ntx64\s120403\engn\psm\psm_entrypoints.C:220> 
<sqloInvokeFnArgs> 
<T:\db2_galileo\ntx64\s120403\engn\sqo\sqloutil.C:1579> 
<sqlriInvokerTrusted> 
<T:\db2_galileo\ntx64\s120403\engn\sqri\sqlriudf.C:8547> 
<sqlriInvokeInvoker> 
<T:\db2_galileo\ntx64\s120403\engn\sqri\sqlriudf.C:7071> 
<sqlricall> 
<T:\db2_galileo\ntx64\s120403\engn\sqri\sqlriudf.C:2013> 
<sqlriSectInvoke> 
<T:\db2_galileo\ntx64\s120403\engn\include\sqlriManageSections.h 
:1582> 
<sqlrr_process_execute_request> 
<T:\db2_galileo\ntx64\s120403\engn\sqr\sqlrr_sql.C:1609> 
<sqlrr_execute> 
<T:\db2_galileo\ntx64\s120403\engn\sqr\sqlrr_req_sql.C:848> 
<pvmPackage::executeSection> 
<T:\db2_galileo\ntx64\s120403\engn\psm\psm_pvm.C:2991> 
<PVM::run> 
<T:\db2_galileo\ntx64\s120403\engn\psm\psm_pvm.C:6004> 
<pvm_entry> 
<T:\db2_galileo\ntx64\s120403\engn\psm\psm_entrypoints.C:220>
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1, Fixpak 2                               * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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

Lösung
First fixed in DB2 v10.1, Fixpak 2
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC94719 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
14.09.2012
17.01.2013
17.01.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.2 FixList
10.5.0.2 FixList