JR45121: GLOBAL MONITORING CONTEXT WIZARD GENERATES ERROR CWMMV0627E

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error description

  • When generating a global monitoring context using the Global
    Monitoring Context wizard, an exception similar to the following
    may occur:
    
    CWMMV0627E: Measure tracking key already in use by
    /GMMyModelMM/DMM/MyMonitoringContext_Cube/MyDimension.
    
    This can occur even if the tracking key in the source monitoring
    context is unique across the monitor model.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the monitor model editor feature   *
    *                  of IBM Integration Designer, and users of   *
    *                  IBM Business Monitor development toolkit.   *
    ****************************************************************
    * PROBLEM DESCRIPTION: When generating a global monitoring     *
    *                      context using the Global Monitoring     *
    *                      Context wizard, an exception similar    *
    *                      to the following may occur:             *
    *                      CWMMV0627E: Measure tracking key        *
    *                      already in use by                       *
    *                      /GMMyModelMM/DMM/MyMonitoringContext_Cu *
    *                      be/MyDimension.                         *
    *                      This can occur even if the tracking     *
    *                      key in the source monitoring context    *
    *                      is unique across the monitor model.     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The problem occurs when a measure in a cube based on the global
    monitoring context uses the same tracking key as a measure in
    a cube based on the root monitoring context.  This is caused
    by copying of the measures from the root monitoring context to
    the global monitoring context.
    Since the tracking key is only used by WebSphere Business
    Monitor, the measures in the global monitoring context do not
    need a tracking key as they are only interacting with the
    root monitoring context in the same monitor model.  These
    tracking keys should not be copied to the global monitoring
    context.
    This problem will be addressed in future maintenance releases
    of IBM Integration Designer Version 8.0.1 and IBM Business
    Monitor development toolkit Version 8.0.1.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR45121

  • Reported component name

    WEB BUS MONITOR

  • Reported component ID

    5724M2400

  • Reported release

    800

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-12-14

  • Closed date

    2013-02-21

  • Last modified date

    2013-02-21

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

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

Fix information

Applicable component levels

  • R750 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Business Monitor

Software version:

800

Reference #:

JR45121

Modified date:

2013-02-21

Translate my page

Machine Translation

Content navigation