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

INGEST UTILITY MIGHT INSERT NULLS INSTEAD OF CORRECT DATA TO NUMERIC
COLUMNS WHEN INPUT FILE SIZE IS HUGE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
INGEST utility might incorrectly insert nulls into nullable 
numeric table columns, instead of non-null data as provided in 
the input data file(s), when total size of the input data 
file(s) is huge. 
 
This problem had been observed when total size of all input data 
files for a single INGEST command is a few hundred megabytes.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 3.                      * 
****************************************************************
Local Fix:
Break down bigger input data files to smaller ones, and run 
separate INGEST command on every single file.
available fix packs:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 Version 10.5 Fix Pack 3. 
 
Note that this is a client side fix.  At a minimum, this fix 
should be applied on the client.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.11.2013
27.02.2014
27.02.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.3 FixList
10.5.0.3 FixList