IBM Support

PJ40697: ANALYZE IMPACT RUN OUT OF MEMORY IN A LARGE PROJECT

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • There is a big ETL project in the workspace. When doing the
    following
    operations, Design Studio will run out of memory:
    1. Do DDL generation in a MQT table
    2. Analyze impact in any model or flows
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * There is a big ETL project in the workspace. When doing the  *
    * following                                                    *
    * operations, Design Studio will run out of memory:            *
    * 1. Do DDL generation in a MQT table                          *
    * 2. Analyze impact in any model or flows                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to fix pack 10.1.0.2                                 *
    ****************************************************************
    

Problem conclusion

  • This problem was first fixed in version 9.7 Fix Pack 3 interim
    fix v20121023 build. At a minimum, this interim fix build should
    be applied on the client (i.e. Design Studio).
    
    After applying this fix, generating DDL in a MQT table or
    analyzing impact in any model/flows will not cause out of memory
    issue.
    Also a switch in the preference is added "Search only opened
    flows when analyzing impact", when use check this option, only
    opened flows be searched with analyzing impacts.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PJ40697

  • Reported component name

    DWE SQL WHSE TO

  • Reported component ID

    5724DWESQ

  • Reported release

    973

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-23

  • Closed date

    2013-08-19

  • Last modified date

    2013-08-19

  • 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

    DWE SQL WHSE TO

  • Fixed component ID

    5724DWESQ

Applicable component levels

  • R973 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCMVBH","label":"DWE - SQL Warehousing Tool"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"973","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
19 August 2013