IBM Support

JR32603: DATABASE FUNCTIONS IN USER DEFINED SQL IN ORACLE ENTPERIRSE STAGE DO NOT WORK WITHOUT ALIASED FIELD NAME FOR FUNCTION OUTPUT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as suggestion for future release.

Error description

  • Using user defined SQL Statemnet in Oracle Enterprise Stage,
    without the aliased fields for the some of the Oracle
    functions can cause jobs to fail.
    
    Example SQL Statement:
    
    SELECT MAX (NUMBER_COLUMN) FROM MYTABLE
    
    will result in following error:
    
    The modify operator has a binding for the non-existent output
    field "NUMBER_COLUMN".
    

Local fix

  • Use aliased field in the SQL Statement like this:
    
    SELECT MAX (NUMBER_COLUMN) NUMBER_COLUMN FROM MYTABLE
    
    This fix is included in 8.0.1 fix pack 3
    

Problem summary

Problem conclusion

  • This change is included in 8.1 Fix Pack 1.
    

Temporary fix

Comments

  • see work-around
    

APAR Information

  • APAR number

    JR32603

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    810

  • Status

    CLOSED SUG

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-04-06

  • Closed date

    2009-04-16

  • 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

Applicable component levels

[{"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