IBM Support

JR37402: MEMORY LEAK IN ORACLE CONNECTOR, WHEN PERFORMING A FETCH OPERATION.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Big amount of heap memory allocated to player executing
    Oracle_Connector_9 operator. Environment variable
    APT_PM_PLAYER_MEMORY is helpful here. You can also trace memory
    usage on O/S side - by checking how much of memory is allocated
    by particular process. In job log attached above it's item 23:
    
       Item #: 23
       Event ID: 409
       Timestamp: 2010-07-23 09:52:16
       Type: Info
       User Name: dsadm
       Message Id: IIS-DSEE-TFPM-00326
       Message: Oracle_Connector_9,0: Heap growth during
    runLocally(): 169492K bytes
    
    It's almost 170MB of memory, which is not reasonable for the
    "Fetch Array Size" setting equal 2000. Moreover - if you
    increase size of MEM_TEST table (add more rows there) the
    consumption will be bigger (it's correlated with Oracle table
    size).
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    DataStage users with jobs that contain Oracle Connector stages
    used to read data from the database.
    ****************************************************************
    PROBLEM DESCRIPTION:
    The Oracle Connector stage is used to read data from an Oracle
    table. Depending on the number of rows fetched from the table,
    the memory consumption in the job changes significantly. The
    more rows are fetched from the database, the more memory is
    consumed. For a very large number of rows the amount of
    allocated memory may reach the system limits and cause the job
    to fail.
    
    ****************************************************************
    RECOMMENDATION:
    Install patch JR37402.
    ****************************************************************
    

Problem conclusion

  • A bug in the connector was fixed that was causing memory leak
    when reading data from the database. This bug was not
    platform-specific.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR37402

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-08-04

  • Closed date

    2010-08-10

  • Last modified date

    2010-08-10

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

       UP

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

Document Information

Modified date:
07 October 2021