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

DB2 ENGINE MAY TRAP IN SQLULIGN() WHILE LOADING DATA FROM IXF FILE.

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
DB2 Engine may trap in  SQLULIGN() while Loading data from IXF 
file 
 
Here is a sample stack: 
 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x000000000000F410 ?unknown + 0x0 
0x090000000827AA28 sqlulign__FP8sqluiiwaPP8SQLUIILTi + 0x580 
0x09000000082847B8 
sqlulirr__FP8sqluiiwaP8sqeAgentiPP10SQLD_VALUEUi + 0x194 
0x090000000837FD28 
@146@sqluGetAndFormatRecords__FP8sqlulacbP13SQLUCACB_TYPEP17SQLU 
_FORMATTER_CBUiPPUciP10sqlz_valuePUcPP10SQLD_VALUET9Pi 
+ 0x8D8 
0x090000000837925C sqluldat__FPUcUi + 0x17F0 
0x0900000005DF2A14 sqloEDUEntry + 0x49C 
</StackTrace> 
 
This apar will address the following: 
1) Fix One Specific Condition that leads to this trap. 
2) Add Defensive Code to avoid this trap 
3) Add diagnostic messages to dump additional information if the 
issue occurs inspite of (1) and (2) above
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2 Engine may trap in  SQLULIGN() while Loading data        * 
* fromIXF fileHere is a sample                                 * 
* stack:<StackTrace>-------Frame------ ------Function +        * 
* Offset------0x000000000000F410 ?unknown +                    * 
* 0x00x090000000827AA28 sqlulign__FP8sqluiiwaPP8SQLUIILTi +    * 
* 0x5800x09000000082847B8sqlulirr__FP8sqluiiwaP8sqeAgentiPP10SQL 
* +                                                            * 
* 0x1940x090000000837FD28@146@sqluGetAndFormatRecords__FP8sqlula 
* 0x8D80x090000000837925C sqluldat__FPUcUi +                   * 
* 0x17F00x0900000005DF2A14 sqloEDUEntry +                      * 
* 0x49C</StackTrace>This apar will address the following:1)    * 
* Fix One Specific Condition that leads to this trap.2) Add    * 
* Defensive Code to avoid this trap3) Add diagnostic messages  * 
* to dump additional information ifthe issue occurs inspite of * 
* (1) and (2) above                                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.5 Fixpak 6 or higher                    * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in Version 9.5 Fixpak 6
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC66422 IC66423 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
01.09.2009
22.06.2010
22.06.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.
Problem behoben lt. FixList in der Version