IBM Support

JR42031: 12,500 CHARACTER LIMITATION AND MISSING LINE BREAKS at CAS layer for Metadata Workbench Data lineage purpose

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • 1) 12,500 characters limitation on the size of the view
    expression
    Details:
    Views that are imported from Teradata Connector have a size
    limitation of 12,500 characters. This causes the views with
    larger expressions to be truncated in Metadata Workbench and
    cannot be parsed for lineage.
    Fix is to change the SQL used within Teradata connector code to
    extract view from Teradata Database.
    
    2) Missing line breaks in the view expression.
    Details:
    The line breaks in the views imported from Teradata Connector
    are missing.
    In MWB, the absence of line breaks as comment terminators
    prevents views from getting linked up to their tables. Teradata
    Database stores only \r characters and does not allow \n
    characters. Teradata connector could see \r characters when the
    view is fetched from the database. However, \r characters went
    missing at CAS layer.
    The fix is to preserve \r characters at CAS Layer so that MWB
    can see the line breaks.
    

Local fix

Problem summary

  • JR42031: FixingTeradata ViewExpression 12,500 CHARACTER
    LIMITATION and Preserving LINE BREAKS at CAS layer for Metadata
    Workbench Data lineage purpose
    

Problem conclusion

  • ERROR DESCRIPTION:
    1) 12,500 characters limitation on the size of the view
    expression.
    Details:
    Views that are imported from Teradata Connector have a size
    limitation of 12,500 characters. This causes the views with
    larger expressions to be truncated in Metadata Workbench and
    cannot be parsed for lineage. Fix is to change the SQL used
    within Teradata connector code to  extract view from Teradata
    Database.
    
    2) Missing line breaks in the view expression.
    Details:
    The line breaks in the views imported from Teradata Connector
    are missing.
    In MWB, the absence of line breaks as comment terminators
    prevents views from getting linked up to their tables. Teradata
    Database stores only \r characters and does not allow \n
    characters. Teradata connector could see \r characters when the
    view is fetched from the database. However, \r characters went
    missing at CAS layer. The fix is to preserve \r characters at
    CAS Layer so that MWB can see the line breaks.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR42031

  • Reported component name

    INFO SRVR PLATF

  • Reported component ID

    5724Q3612

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-02-27

  • Closed date

    2012-03-21

  • Last modified date

    2012-09-03

  • 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

    INFO SRVR PLATF

  • Fixed component ID

    5724Q3612

Applicable component levels

  • R850 PSY

       UP

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

Document Information

Modified date:
07 October 2021