IBM Support

JR32746: OMD MATCHING SERVICE CAUSES OUTOFMEMORYERRORS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • The code for the OMD"matching" service
    (com.ascential.omd.matching.server.impl.MatchingPojo), is
    executing an XMQL query (select distinct y from x in
    ASCLModel::Stage, y in x->of_JobDef) without a proxy strategy.
    
    Here is the relevant portion of the stack trace, which shows the
    class that is executing the query:
    
     at
    com.ascential.xmeta.client.repository.query.impl.DefaultQueryRes
    ult.hasNext(DefaultQueryResult.java:199)
    at
    com.ascential.omd.matching.server.impl.MatchingPojo.sequentialSc
    anASCLJobDefClass(MatchingPojo.java:3393)
    at
    com.ascential.omd.matching.server.impl.MatchingPojo.findSimpleSt
    ageMatches(MatchingPojo.java:3156)
    at
    com.ascential.omd.matching.server.impl.MatchingPojo.checkCRLTabl
    es(MatchingPojo.java:2500)
    at
    com.ascential.omd.matching.server.impl.MatchingPojo.checkByLocat
    orComponentLocator(MatchingPojo.java:2239)
    at
    com.ascential.omd.matching.server.impl.MatchingPojo.findMatching
    Locator(MatchingPojo.java:1549)
    at
    com.ascential.omd.matching.server.impl.MatchingPojo.generateMatc
    hingForRuntimeBinding(MatchingPojo.java:180)
    at
    com.ascential.omd.matching.server.impl.MatchingBean.generateMatc
    hingForRuntimeBinding(MatchingBean.java:155)
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    MWB 8.0 OMD matching service
    ****************************************************************
    PROBLEM DESCRIPTION:
    When running the  OMD "matching" service from WB 8.0, caused
    OOM.
    ****************************************************************
    RECOMMENDATION:
    Upgrade to MWB 8.0.1
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR32746

  • Reported component name

    METADATA WORKBE

  • Reported component ID

    5724S4100

  • Reported release

    800

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-04-20

  • Closed date

    2009-08-05

  • Last modified date

    2009-08-05

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • OMD
    

Fix information

Applicable component levels

  • R800 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS3GFL","label":"InfoSphere Metadata Workbench"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
05 August 2009