IBM Support

JR32598: ODBC CONNECTOR STAGE FAILS TO EXECUTE SQL STATEMENT WHEN CONFIGURED TO READ IN PARALLEL AND A WHERE CLAUSE IS USED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The problem occurs when a job parameter is used for the contents
    of the 'WHERE' clause (including the 'WHERE' keyword itself)
    within the ODBC connector stage. When the partitioning feature
    is used within the ODBC connector, it alters the user supplied
    SQL statement at runtime by appending a WHERE clause to
    restrict the data returned.  This happens for each node in the
    configuration file.  The problem is that when the user SQL
    statement contains a job parameter, it does not do the job
    parameter replacement FIRST before it alters the SQL statement.
    The resulting effect is that the SQL statement returns a
    syntax error during job execution because it has been made
    invalid by the process of appending the additional where
    clause.
    

Local fix

  • This fix is included in 8.0.1 fixpack 3
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    ODBC CONNECTOR STAGE FAILS TO EXECUTE SQL STATEMENT WHEN
    CONFIGURED TO READ IN PARALLEL AND A WHERE CLAUSE IS USED
    ****************************************************************
    PROBLEM DESCRIPTION:
    The problem occurs when a job parameter is used for the
    contentsof the 'WHERE' clause (including the 'WHERE' keyword
    itself)    within the ODBC connector stage. When the
    partitioning feature  is used within the ODBC connector, it
    alters the user supplied  SQL statement at runtime by appending
    a WHERE clause to restrict the data returned.  This
    happens for each node in the  configuration file.  The problem
    is that when the user SQL  statement contains a job
    parameter, it does not do the job parameter replacement FIRST
    before it alters the SQL statement. The resulting effect
    is that the SQL statement returns a syntax error during job
    execution because it has been made   invalid by the
    process of appending the additional where clause.
    ****************************************************************
    RECOMMENDATION:
    Apply the APAR
    The fix has been included in the IS 8.1 FP1. Apply the FixPack1
    for IS 8.1.
    ****************************************************************
    

Problem conclusion

  • Improved the SQL parsing capabilities in the ODBC Connector.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR32598

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-04-06

  • Closed date

    2009-05-19

  • Last modified date

    2010-12-09

  • 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

  • R810 PSY

       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.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
09 December 2010