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

CRASH IN SQLUGETANDFORMATRECORDS FUNCTION WHILE RUNNING LOAD COMMAND

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Instance may crash with a stack similar to the following when 
running LOAD command against a table.  We might hit this problem 
only when both WARNINGCOUNT option and DUMPFILE modifier are 
used, and the LOAD operation hit the warningcount limit. 
 
 0x000000000000F4E8 ?unknown + 0x0 
  0x09000000059814E0 
@72@sqluWriteDumpFile__FP8sqlulacbP11formattercbP8sqlucacbPUcUc 
+ 0x340 
  0x090000000597CB24 
@72@sqluGetAndFormatRecords__FP8sqlulacbP8sqlucacbP11formattercb 
UiPPUciP10sqlz_valuePUcPP10SQLD_VALUET9Pi 
+ 0x554 
  0x0900000005BB89A8 sqluldat__FPUcUi + 0x630 
  0x0900000004CB04B8 
sqloCreateEDU__FPFPcUi_vPcUlP13SQLO_EDU_INFOPi + 0x26C 
  0x0900000004CAB1E4 sqloSpawnEDU + 0x234 
  0x0900000005FB7C6C 
@72@sqlulInitOneEDU__FP8sqlucacbP11SqluEduInfoP12SQLU_EDU_ARGPUc 
P13SQLO_EDU_INFOUiPFPcUi_vi 
+ 0x138 
  0x0900000005FB799C 
@72@sqlulInitNFormatters__FP8sqlucacbP11SqluEduInfoP12SQLU_EDU_A 
RGP13SQLO_EDU_INFOPUi 
+ 0x10C 
  0x0900000005FA53AC 
@72@sqlulCreateQAndEDU__FP8sqlucacbP8sqluvlcb + 0x2A0 
  0x0900000005FA08CC 
sqluvload__FPUcT1P8SQLP_LSNP7sqlubmhPP15sqlu_media_listT5UcP26sq 
luCLoadRequestDescriptorP8sqluvlcbPi 
+ 0x1DE8 
  0x0900000005F9E758 
@72@call_sqluvload__FP20sqle_agent_privatecbP12SQLB_GLOBALSP26sq 
luCLoadRequestDescriptorP20sqlu_loadapi_load_cbiT5PiT7 
+ 0xA64
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All LOAD users                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Instance may crash with a stack similar to the following     * 
* when running LOAD command against a table.  We might hit     * 
* this problem only when both WARNINGCOUNT option and DUMPFILE * 
* modifier are used, and the LOAD operation hit the            * 
* warningcount limit.                                          * 
*                                                              * 
* 0x000000000000F4E8 ?unknown + 0x0                            * 
* 0x09000000059814E0                                           * 
* @72@sqluWriteDumpFile__FP8sqlulacbP11formattercbP8sqlucacbPUcU 
* + 0x340                                                      * 
* 0x090000000597CB24                                           * 
* @72@sqluGetAndFormatRecords__FP8sqlulacbP8sqlucacbP11formatter 
* + 0x554                                                      * 
* 0x0900000005BB89A8 sqluldat__FPUcUi + 0x630                  * 
* 0x0900000004CB04B8                                           * 
* sqloCreateEDU__FPFPcUi_vPcUlP13SQLO_EDU_INFOPi + 0x26C       * 
* 0x0900000004CAB1E4 sqloSpawnEDU + 0x234                      * 
* 0x0900000005FB7C6C                                           * 
* @72@sqlulInitOneEDU__FP8sqlucacbP11SqluEduInfoP12SQLU_EDU_ARGP 
* + 0x138                                                      * 
* 0x0900000005FB799C                                           * 
* @72@sqlulInitNFormatters__FP8sqlucacbP11SqluEduInfoP12SQLU_EDU 
* + 0x10C                                                      * 
* 0x0900000005FA53AC                                           * 
* @72@sqlulCreateQAndEDU__FP8sqlucacbP8sqluvlcb + 0x2A0        * 
* 0x0900000005FA08CC                                           * 
* sqluvload__FPUcT1P8SQLP_LSNP7sqlubmhPP15sqlu_media_listT5UcP26 
* + 0x1DE8                                                     * 
* 0x0900000005F9E758                                           * 
* @72@call_sqluvload__FP20sqle_agent_privatecbP12SQLB_GLOBALSP26 
* + 0xA64                                                      * 
* ...                                                          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 4.                       * 
****************************************************************
Local-Fix:
1.  Do not use LOAD options WARNINGCOUNT and DUMPFILE together 
in the same Load command 
2.  The issue may occur only after reaching the Warning count. 
You may want to address the Warning message to avoid DB2 from 
returning any warnings and reaching the WARNINGCOUNT limit.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in DB2 Version 9.7 Fix Pack 4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
09.11.2010
19.04.2011
19.04.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP4
Problem behoben lt. FixList in der Version
9.7.0.4 FixList