IBM Support

JR59186: When DB2 Connector uses Derivation the columns mismatch occurs and the job aborts with error

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When in DB2 Connector the Derivation is specified for a column
    to return the result of an expression, schema reconciliation
    fails as the column's name cannot be matched with the result of
    an expression named like eg.: EXPR1.
    In case of migration from DB2API to DB2CC, despite the
    Derivation expression is correctly migrated, a job aborts.
    The cause of this issue is that binding by Name is done (by
    default).
    Job aborts with error:
    CopyOfpmrCount1..DB2_Connector_0: Schema reconciliation failed:
    The column names defined on the link do not match those of the
    external resource
    CopyOfpmrCount1..DB2_Connector_0.DSLink2: DSP.Open GCI
    $DSP.Open error -100.
    CopyOfpmrCount1..Sequential_File_1.IDENT1:
    |CopyOfpmrCount1..DB2_Connector_0.DSLink2: DSP.Open GCI
    $DSP.Open error -100.|
    

Local fix

  • If we specify an alias, the column is matched by its name and
    job runs OK - the issue is not reproduced.
    Another way to make it work, instead of using alias, is to use
    the DB2 Connector's property "Prefix for expression columns",
    which by default is EXPR.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of DB2 Connector stage on Server Canvas, using Derivation
    for a column.
    ****************************************************************
    PROBLEM DESCRIPTION:
    When in DB2 Connector the Derivation is specified for a column
    to return the result of an expression, schema reconciliation
    fails as the column's name cannot be matched with the result of
    an expression named like eg.: EXPR1.
    In case of migration from DB2API to DB2CC, despite the
    Derivation expression is correctly migrated, a job aborts.
    The cause of this issue is that binding by Name is done (by
    default).
    ****************************************************************
    RECOMMENDATION:
    Apply the patch JR59186
    ****************************************************************
    

Problem conclusion

  • Implemented the code change in DB2 Connector so when a column
    Derivation is used, columns are binded by Position.
    As a result, the job with Derivation does not abort and the
    migrated job works without any changes.
    However, when "Prefix for expression columns" (EXPR) is used in
    the column name - the default binding by Name is performed to
    keep previous behavior in this case.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR59186

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    B50

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-02-26

  • Closed date

    2018-08-21

  • Last modified date

    2018-08-21

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

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

Fix information

  • Fixed component name

    WIS DATASTAGE

  • Fixed component ID

    5724Q36DS

Applicable component levels

  • RB50 PSY

       UP

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

Document Information

Modified date:
03 September 2021