IBM Support

JR34242: ROWS REJECTED WHEN TRAILING SPACES ARE IN SQL STATEMENT IN TERADATA API STAGE AFTER UPGRADING TO TTU 12.0.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • There are 2 trailing spaces after "semi-colon" .If there is no
    semi-colon in the statement, then it is taken a single SQL
    request.  (semi-colon is statement separator for Teradata SQL).
    
    As per original design, TD-API stage does not parse the
    "user-defined-SQL". So, the above sql-statement is read as is, &
    is treated as multi-statement request and the following SQLs
    are processed separately:
    
    1) "Insert into T1 (  PARTY_ID,  GROUP_NM,  BATCH_ID,   JOB_ID,
    RUN_ID ) Select  PARTY_ID, GROUP_NM, 1, 1, 1 from  GRP where
    ROW_STATUS_IND = 1;"
    
    2) "  "
    
    While the "blank statement" (shown in 2 above), is being
    processed without any error, by V2R6.2 DBS, Teradata v12 is
    giving the following message, when the 'blank statement' is
    submitted:
    
    ==================
    tapi_grp: Syntax error: expected something between the beginning
    of the request and the end of the request.
    ==================
    
    DataStage 7.5.2 on RedHat Linux
    

Local fix

  • Remove trailing spaces from the user-defined SQL
    
    This fix is included in 8.0.1 fixpack 3
    

Problem summary

  • ****************************************************************
    
    USERS AFFECTED:
    Trailing blanks after semi-colon in user-defined-sqls, when run
    against Teradata v12, the users encounter this issue.
    ****************************************************************
    PROBLEM DESCRIPTION:
    Removing the "trailing blanks" in user-defined-sqls.
    ****************************************************************
    RECOMMENDATION:
    Install the patch.
    ****************************************************************
    

Problem conclusion

  • The issue fixed as part of JR34242 is for "trailing blanks" in
    user-defined-SQLs. While the "trailing blanks" are accepted by
    Teradata V2R6.x databases, Teradata v12 DBS is throwing a
    warning, which gets fixed with the patch of JR34242.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR34242

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    752

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-09-10

  • Closed date

    2011-08-08

  • Last modified date

    2011-08-08

  • 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

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

Document Information

Modified date:
08 August 2011