IBM Support

JR29759: COLUMN IMPORT FAILS WHEN USTRING COLUMN CONTAINS A COMBINATION OF SPECIFIC CHARACTERS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • When a customer tried to import a sequential file which contains
    multiple fields delimited by '|' using Column Import stage,
    he got various errors like below:
    
    - Fatal: Column_Import_7,0: Failure during execution of operator
    logic.
    - Warning: Column_Import_7,0: Field "NULL_S_ORG_NAME" has import
    error and no default value; data: , at offset: 92
    
    After the investigation, we found the problem occurs when a
    ustring column contains a combination of specific characters
    of which the subset is equal to the delimiter in UTF-16
    encoding.
    For example, the following strings caused the subject problem:
    - A Japanese Kanji character "Mei" + A Japanese full-width
    space:  0x957C + 0x0030
    - A Japanese Kanji character "Kasu" + A Japanese full-width
    space: 0xD67C + 0x0030
    - A Japanese Kanji character "Tou" + A Japanese full-width
    space:  0x737C + 0x0030
    Also,
    - A field delimiter '|': 0x7C00
    

Local fix

  • modify a generated osh directly
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    RH Linux IS 8.0.1 fpa
    ****************************************************************
    PROBLEM DESCRIPTION:
    Column import fails when ustring column contains a combination
    of specific characters
    ****************************************************************
    RECOMMENDATION:
    Install the patch patch_JR29759_pxengine_fp1_linux.tar
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR29759

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    801

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-06-30

  • Closed date

    2008-07-28

  • Last modified date

    2008-07-28

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

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

Modules/Macros

  • LIBORCH
    

Fix information

Applicable component levels

  • R801 PSN

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
28 July 2008