IBM Support

IT08551: INGEST: SQL0804N OR INCORRECT DECIMAL DATA LOADED WHEN DECIMAL IS IN ASCII AND PRECISIONS DO NOT MATCH

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • 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.
    

Local fix

  • 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.
    

Problem summary

  • ****************************************************************
    * 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.                      *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 Version 10.1 Fix Pack 5.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT08551

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-04-25

  • Closed date

    2017-01-20

  • Last modified date

    2017-01-20

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    IT09394

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RA10 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
20 January 2017