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

Crash in SQLUGETANDFORMATRECORDS function while running load command with
WARNINGCOUNT and DUMPFILE options.

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
Instance may crash with a stack similar to the following when 
running LOAD command with WARNINGCOUNT and DUMPFILE options. 
 
 
 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 Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* When using LOAD with the options WARNINGCOUNT and DUMPFILE   * 
* together in the same Load command.                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Instance may crash with a stack similar to the following     * 
* when running LOAD command against a table.                   * 
*                                                              * 
* 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 LUW db2_v91fp10                               * 
****************************************************************
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.
available fix packs:
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC72499 IC72500 IC72501 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.04.2010
16.06.2011
16.06.2011
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.10 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.