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

TRAP IN Sqlak_CallbDrdaInput WHEN IMPORTING XML DATA AND USING THE
COMPOUND OPTION

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
During import of XML data, db2bp.exe crashes with a C000 0005 
exception in db2app.dll. Here is a portion of the Trap (from DB2 
v9.5 FP3a, but problem also occurs in V9.1): 
 
<Trap> 
<Header> 
DB2 build information: DB2 v9.5.301.436 s081210 SQL09053 
timestamp: 2009-03-17-10.29.10.229000 
uname: S:Windows 
comment: WR21427 
process id: 5500 
thread id: 5260 
</Header> 
<SystemInformation> 
Number of Processors: 2 
Processor Type: x86 Family 6 Model 15 Stepping 6 
OS Version: Microsoft Windows XP, Service Pack 2 (5.1) 
Current Build: 2600 
</SystemInformation> 
<MemoryInformation> 
<Usage> 
Physical Memory:    3326 total,    1809 free. 
Virtual Memory :    2047 total,    1953 free. 
Paging File    :    5210 total,    3380 free. 
Ext. Virtual   :       0 free. 
</Usage> 
</MemoryInformation> 
<SignalDetails> 
Exception C0000005 Occurred 
Exception Address = 6C012A33 
Other Unknown access fault 
</SignalDetails> 
<Registers> 
GS  : 0000     FS  : 003B     ES  : 0023     DS  : 0023 
EDI : 036F3410 ESI : 01C60370 EAX : DB2CAFE8 EBX : 01C6E484 
ECX : DB2CAFE8 EDX : 036F3CE0 
EBP : 0012DFBC EIP : 6C012A33 EFLG: 00010286 ESP : 0012DF18 
CS  : 001B     SS  : 0023 
</Registers> 
<POFDisassembly> 
<![CDATA[ 
Failing instruction at 6C012A33 offset: 000008A7 in 
<?sqlak_callbDrdaInput@@YAHPAUdb2UCinterface@@@Z> <NotFound:-1> 
0x6C012A13 ADD          EAX,EDI 
0x6C012A15 MOV          ECX,DWORD PTR [EBP-18H] 
0x6C012A18 IMUL         ECX,+2CH 
0x6C012A1B LEA          EAX,DWORD PTR [EAX+ECX+10H] 
0x6C012A1F MOV          ECX,DWORD PTR [EAX+8] 
0x6C012A22 TEST         ECX,ECX 
0x6C012A24 JZ           6C012B83H 
0x6C012A2A MOV          EDX,DWORD PTR [EDX+4] 
0x6C012A2D MOV          DWORD PTR [ESI+20H],EDX 
0x6C012A30 MOV          EAX,DWORD PTR [EAX+8] 
0x6C012A33 MOV          EAX,DWORD PTR [EAX] 
<<<< 
0x6C012A35 MOV          DWORD PTR [ESI+34H],EAX 
0x6C012A38 TEST         EAX,EAX 
0x6C012A3A JL           6C432FC2H 
0x6C012A40 MOV          DWORD PTR [EBP-58H],EAX 
0x6C012A43 TEST         EAX,EAX 
0x6C012A45 JZ           6C432FA6H 
0x6C012A4B MOV          EAX,DWORD PTR [ESI+8] 
0x6C012A4E MOV          EDX,DWORD PTR [ESI+1CH] 
0x6C012A51 MOV          DWORD PTR [EBP],EDI 
]]></POFDisassembly> 
<StackTrace> 
<![CDATA[ 
--EBP------EIP------ARGS----------------------------- 
0012DFBC 6C012A33 01C614B8 01C825A0 00002113 01C825A0 offset: 
000008A7 in <?sqlak_callbDrdaInput@@YAHPAUdb2UCinterface@@@Z> 
<NotFound:-1> 
0012E058 6C12567A 01C614B8 00000000 036F3420 00000009 offset: 
000003A6 in <?sqljrGenSqlDta@@YAHPAUdb2UCinterface@@I@Z> 
<sqljrbni.C:662> 
0012E090 6C109FCF 01C614B8 00000000 5C617461 6C697455 offset: 
000000D5 in 
<?sqljrDrdaArExecute@@YAHPAUdb2UCinterface@@PAUUCstpInfo@@@Z> 
<sqljrintrfc.C:2715> 
0012E46C 6C002C15 00000026 00000000 00000000 00000000 offset: 
000006E1 in <_sqlacall@20> <sqlakmain.C:4311> 
0012E51C 6C2D380A 0012F390 1C080007 00000004 0012FA18 offset: 
000039C2 in 
<?sqluimpm@@YAXPAHPAUsqluecb@@PAUsqlca@@EPAPAEPAUSQLO_MEM_POOL@@ 
000PAUdb2ImportOut@@@Z> <sqluimpm.SQC:5966> 
0012FB74 6C2D1F18 6C68D590 01C90060 0053C5DC 00000033 offset: 
000020D0 in 
<?sqluimpm@@YAXPAHPAUsqluecb@@PAUsqlca@@EPAPAEPAUSQLO_MEM_POOL@@ 
000PAUdb2ImportOut@@@Z> <sqluimpm.SQC:4320> 
0012FC80 6C2FB74C 00000000 0053E74C 0055E648 0053C7A8 offset: 
00000374 in 
<?sqluimpt@@YAXPAD0PAUsqlu_media_list@@PAUsqldcol@@PAUsqllob@@0P 
AUsqlchar@@0HPAUdb2ImportIn@@PAUdb2ImportOut@@PAH1PAXPAUsqlca@@@ 
Z> <sqluimpt.C:787> 
0012FD30 6C2D8D0D 008A18BC 0012FD4C 0053C5DC 0053C7A0 offset: 
00000247 in <_db2Import.@12> <sqluapi.C:1875> 
0012FD88 0041F3B2 00000000 0288DBCC 0012FDB0 6CFC012A offset: 
000000EA in <?clpbp_exe_sqluimpt@@YAHXZ> <clpbcmd1.C:19790> 
0012FF08 004764D6 0012FF68 0012FF7C 0012FF7C 00475FFF offset: 
0000049A in <?clp_bp_con@@YAHXZ> <clpbp.C:1071> 
0012FF68 00475FFF 005BC3B8 00000000 005BC3C8 00000000 offset: 
000001CF in <_main> <clpbp.C:413> 
0012FFC0 0052AC16 0000000D 3242445C 7FFD7000 8054A6ED offset: 
0000010F in <__tmainCRTStartup> 
<f:\qfe\vctools\crt_bld\self_x86\crt\src\crtexe.c:597> 
0012FFF0 7C816FD7 0052AD5F 00000000 78746341 00000020 
]]></StackTrace>
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of IMPORT on a table containing XML data               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 Fix Pack 1                               * 
****************************************************************
Local-Fix:
Work Around: Remove the COMPOUND option from the IMPORT 
statement
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Lösung
Problem fixed in DB2 V9.7 Fix Pack 1
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.10.2009
23.02.2010
23.02.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP1
Problem behoben lt. FixList in der Version
9.7.0.1 FixList