IBM Support

JR46719: TRACKING GROUP VIEW CREATION FAILS WHEN TRACKED FIELD NAME MATCHES TRACKING GROUP TABLE OR VIEW COLUMN NAMES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • When tracking definitions are created for a tracking group,
    creation of the view for the tracking group in the Performance
    Data Warehouse database will fail if a generated column name
    matches standard column names used for tracking group tables
    and views.  An example of a tracked field name that results in
    an attempt to create a duplicate column name in a tracking
    group view is "SNAPSHOT".
    

Local fix

  • In Process Designer, ensure that validation errors for variable
    names are corrected before generating or updating tracking
    definitions for a process application.  (Names of some columns
    for the tracking group tables and views are based on the names
    of tracked fields in the process application.)
    
    Following are steps to address prior view creation failures.
    
    1. Review the contents of the NEW_COLUMN_NAME column of the
    LSW_COLUMN table in the Performance Data Warehouse database.
    Determine if any values in the NEW_COLUMN_NAME column match the
    following reserved column names.
    
    TRACKING_POINT_VALUE_ID
    SYSTEM_ID
    SNAPSHOT_ID
    TRACKING_GROUP_ID
    TRACKING_POINT_ID
    TASK_ID
    FUNCTIONAL_TASK_ID
    TIME_STAMP
    SNAPSHOT
    ACRONYM
    TIME_STAMP_YEARS
    TIME_STAMP_QUARTERS
    TIME_STAMP_MONTHS
    TIME_STAMP_WEEKS
    TIME_STAMP_DAYS
    
    2. For any rows in LSW_COLUMN where NEW_COLUMN_NAME matches the
    values listed in step one, modify the NEW_COLUMN_NAME value to
    make it unique, such as by adding the number '1' to the end.
    
    3. Also update the corresponding tracked field name in the
    tracking group definition in Process Designer.
    
    4. Update tracking definitions.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of BPM Express, BPM Standard, and     *
    *                  BPM Advanced.                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: When updating Performance Data          *
    *                      Warehouse tracking definitions, view    *
    *                      creation fails because the name of a    *
    *                      tracked field matches a reserved        *
    *                      column name for tracking group tables   *
    *                      or views.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The view creation logic that is part of updating tracking
    definitions did not check and prevent use of reserved column
    names that are standard column names for tracking group tables
    and views.
    This issue will be addressed in a future release of IBM
    Business Process Manager.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR46719

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    801

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-05-21

  • Closed date

    2013-09-13

  • Last modified date

    2013-09-13

  • 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

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
13 September 2013