home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC84390 Status: Closed

IMPORT UTILITY CRASHES DUE TO MISSED COLUMN

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
A table originally contains a generated column, a LOB column and 
some other columns, then data in this table is exported to an 
IXF file. When recreating this table, the LOB column is missed 
(other columns unchanged) for some reason so that subsequent 
IMPORT from the IXF file traps with SIGSEGV (signal #11). The 
stack trace looks like the following: 
 
-------Frame------ ------Function + Offset------ 
0x090000004E919EB8 shiftDescInfo__13sqluCImpTableFPUcPi + 0x244 
0x090000004EACD180 
ShiftSqldaForDefaults__13sqluCImpTableFP7sqluecb + 0x24 
0x090000004E362D50 
sqluimpm__FPiP7sqluecbP5sqlcaUcPPUcP13SQLO_MEM_POOLN31P12db2Impo 
rtOut 
+ 0x3A18 
0x090000004E758420 
sqluimpt__FPcT1P15sqlu_media_listP7sqldcolP6sqllobT1P7sqlcharT1i 
P11db2ImportInP12db2ImportOutPiT3PvP5sqlca 
+ 0x8B8 
0x090000004E7577A4 db2Import + 0x5C4 
0x0000000100039028 clpbp_exe_sqluimpt__Fv + 0x1C8 
0x0000000100001794 clp_bp_con__Fv + 0x634 
0x0000000100000B24 main + 0x224 
 
Impact: 
IMPORT traps and the connection is terminated so that a user has 
to reconnect to the database to do other operations.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See ERROR DESCRIPTION.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v9.7 Fixpack 6                                    * 
****************************************************************
Local Fix:
Use correct DDL to recreate the target table and try IMPORT 
again.
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
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

Solution
First fixed in v9.7 Fixpack 6.  At minimum this fix should be 
applied to the server.
Workaround
See LOCAL FIX.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
16.04.2013
16.04.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList