IBM Support

LI74187: DATA TRUNCATION WITHOUT A WARNING MESSAGE WHEN EXPORTING FROM DB2 V8 FOR Z/OS TO DB2 V9.1 FOR LINUX.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Data trancation might happen during export if the codepages ued
    are unsupported.
    For eg : "unicode client to non-unicode server not supported"
    and the truncation event is known in such cases.
    
    Fix includes to give a global (i.e. not per-row) SQL3132W
    warning if a truncation may potentially occur.  This is the
    current behaviour for DB2 LUW that is not working with DB2
    z/OS, and the fix is to make DB2 z/OS work like DB2 LUW.
    
    Receiving a warning means "a truncation may occur with
    that column".
    With the fix, "no warning" will mean "there was no truncation",
    but a warning means "there may or may not be a truncation with
    user's actual data".
    

Local fix

  • Users should export data into the same codepage if possible so
    that there will be no codepage conversion issue during export.
    The import/load may need a codepage conversion though.
    

Problem summary

  • Data trancation might happen during export if the codepages ued
    
    are unsupported.
    For eg : "unicode client to non-unicode server not supported"
    and the truncation event is known in such cases.
    
    Fix includes to give a global (i.e. not per-row) SQL3132W
    warning if a truncation may potentially occur.  This is the
    current behaviour for DB2 LUW that is not working with DB2
    z/OS, and the fix is to make DB2 z/OS work like DB2 LUW.
    
    Receiving a warning means "a truncation may occur with
    that column".
    With the fix, "no warning" will mean "there was no truncation",
    but a warning means "there may or may not be a truncation with
    user's actual data".
    

Problem conclusion

  • DATA TRUNCATION WITHOUT A WARNING MESSAGE WHEN EXPORTING
    FROM DB2 V8 FOR Z/OS  TO DB2 V9.1 FOR LINUX.
    

Temporary fix

  • Users should export data into the same codepage if possible so
    that there will be no codepage conversion issue during export.
    The import/load may need a codepage conversion though.
    

Comments

APAR Information

  • APAR number

    LI74187

  • Reported component name

    DB2 UDE ESE LIN

  • Reported component ID

    5765F4104

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-07-07

  • Closed date

    2010-04-30

  • Last modified date

    2010-04-30

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

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

    LI75095 IC66234

Fix information

  • Fixed component name

    DB2 UDE ESE LIN

  • Fixed component ID

    5765F4104

Applicable component levels

  • R910 PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
17 October 2021