IBM Support

JR31521: MEMORY LEAK IN TD CONNECTOR SETNATIVESTRING", AND "GETNATIVESTRING" FUNCTIONS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • There were 2 memory leak issues identified in the TD Connector
    since decimal 38 support was added via  125205
    
    
    1.found the heap size increases in 64 bytes while processing
    each record. These were for columns of type decimal.
    CC_PXAccessor::getBigDecimal() returns a pointer to a
    CC_BigDecimal object that is created in the function. This
    pointer is not saved under CC_PXAccessor and the object needs to
    be freed by its caller.  But the caller,
    CC_TeraDBStmtParamDecimal::writeBuffer(), did not do that. By
    ading the call of CC_BigDecimal::destroyInstance() to
    CC_TeraDBStmtParamDecimal::writeBuffer() and verified the heap
    size becomes constant and does not increase at all.
    
    2. There appears to be an memory leak in
    functions:
    "setNativeString", and "getNativeString" functions (in
    DAAPI-PX/fcl/PX_Accessor.cpp).
    
    Verified few TDCC jobs (both read & write), involving "charset
    conversion" and found that the issue is getting reproduced.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users using "decimal datatype" and when there is
    "charset" conversion involved.
    ****************************************************************
    PROBLEM DESCRIPTION:
    The issue is  actually "memory leak" in certain specific
    scenarios (when using "decimal" datatype and when there is
    "charset" conversion invovled).
    ****************************************************************
    RECOMMENDATION:
    Install the patch provided as part of APAR: JR31427.
    ****************************************************************
    

Problem conclusion

  • Issed fixed in CC_Framework and in TD-Connector as well. Patch
    is provided as part of the APAR: JR31427, which contains the
    fix for this issue as well.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR31521

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-12-22

  • Closed date

    2009-01-13

  • Last modified date

    2009-01-13

  • 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 PSN

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

Document Information

Modified date:
13 January 2009