DB2 FOR LUW / DB2FORLUW / A10 - DB2

A problem in injest logic could result in random SQL0804N 
messages or incorrect decimal data being loaded.   
 
The problem can occur only when both of the following are true: 
- The decimal number is represented in ASCII in the input file 
or pipe. 
- That ASCII representation excluding leading zeros has a 
precision less than the default precision or less than the 
precision specified on the field definition (if any). 
For example: 
000000000064913.   precision excluding leading zeros is 5 
100000000064913.   precision excluding leading zeros is 15 
 
 
The precision of a decimal field can be determined as follows: 
- If the INGEST command omits the field definition list, then 
the precision is the same as the precision of the corresponding 
table column. 
- If the INGEST command specifies a field definition list but 
the precision of a decimal field is not specified, the precision 
defaults to 5. 
- Otherwise, the precision is whatever is specified on the field 
definition. 
 
 
The problem is more likely when ingesting input files that are 
about 400 MB in size or larger.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of the DB2 LUW ingest utility.                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5.                      * 
****************************************************************

Ensure that the number of digits in decimal values in the input 
file or pipe is always the same as the precision specified on 
the field definition  or  the same as  default precision if the 
field definition or precision are omitted.

First fixed in DB2 Version 10.1 Fix Pack 5.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

25.04.2015
20.01.2017
20.01.2017