PJ39183: COLUMN MAPPING DOESN'T WORK AS EXPECTED WHEN CONNETING SQL QUERY SOURCE OPERATOR AND TABLE TARGET OPERATOR

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • If you connect a SQL Query Source operator to a Table Target
    operator in a data flow and then change the column mapping of
    Table Target operator, the generated code won't have the
    expected change. As a result, the execution of the data flow
    will fail.
    
    For Example:
    
    In SQL Query Source operator,  if you use the following select
    statement,
    
          SELECT Column1, Column2 , Column3  FROM TABLENAME,
    
     but there's different sequence in table target that is "
    Column3,  Column1 , Column2", changing the column mapping
    sequence won't change  the generated SQL code.
    

Local fix

  • Workaround : None
    Interimfix SQW_9.7.2.v20110629 or later fixes
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * In ISW9.7.2 release, when connecting SQL Query Source        *
    * operator                                                     *
    * and Table Target operator in dataflow,  if changing          *
    * the column mapping of table target operator, the code        *
    * generated  won't have the change.  In this scenario .        *
    * Dataflow will be executed with failed result.                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * If you connect a SQL Query Source operator to a Table Target *
    * operator in a data flow and then change the column mapping   *
    * of                                                           *
    * Table Target operator, the generated code won't have the     *
    * expected change. As a result, the execution of the data flow *
    * will fail.                                                   *
    *                                                              *
    * For Example:                                                 *
    *                                                              *
    * In SQL Query Source operator,  if you use the following      *
    * select                                                       *
    * statement,                                                   *
    *                                                              *
    *       SELECT Column1, Column2 , Column3  FROM TABLENAME,     *
    *                                                              *
    * but there's different sequence in table target that is "     *
    * Column3,  Column1 , Column2", changing the column mapping    *
    * sequence won't change  the generated SQL code.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply SQW_9.7.1.v20110511 or upgrade to InfoSphere Warehouse *
    * 9.7.7                                                        *
    ****************************************************************
    

Problem conclusion

  • The column mapping is correct after applying SQW_9.7.1.v20110511
    or later hotfix package
    

Temporary fix

Comments

APAR Information

  • APAR number

    PJ39183

  • Reported component name

    DWE DESIGN STUD

  • Reported component ID

    5724DWEDS

  • Reported release

    972

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-06-30

  • Closed date

    2013-02-25

  • Last modified date

    2013-02-25

  • 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

    DWE DESIGN STUD

  • Fixed component ID

    5724DWEDS

Applicable component levels

  • R972 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

InfoSphere Warehouse
DWE - Design Studio

Software version:

972

Reference #:

PJ39183

Modified date:

2013-02-25

Translate my page

Machine Translation

Content navigation