IBM Support

IJ24790: SLOW PERFORMANCE OR TIMEOUT WHEN VIEWING ASSOCIATED WORK ORDERS IN MULTIASSETLOCCI TABLE FOR ASSET ON A WORK ORDER

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

  • DESCRIPTION:
    The MULTIASSETLOCCI table is used to relate work to assets and
    locations, providing a one-to-many relationship between a work
    order and those objects. Within the Work Order applications
    (WOTRACK / QUICKREP), the list of related MULTIASSETLOCCI
    records is displayed quickly because there is a supporting
    index. However, when using the Asset application/Work tab to
    view Work Order records, the query uses the MULTIASSETLOCCI
    table (via the MULTIASSETLOCCIWO relationship) and takes an
    extremely long time to execute when the WORKORDER and
    MULTIASSETLOCCI tables have millions of records, because there
    is no index to support the query executed as part of the
    ASSET/MULTIASSETLOCCIWO relationship. The same is true when you
    execute the Locations/Work Details dialog.
    The User can create a workaround to this issue. A Relationship
    is added to the ASSET Object and it uses an Index that is added
    to the MULTIASSETLOCCI Object, configured and made persistent
    as follows in the Database Configuration application:
    Object: ASSET
    On the Relationships tab:
    Relationship: MULTIASSETLOCCI
    Child Object: MULTIASSETLOCCI
    Where Clause: assetnum=:assetnum and siteid=:siteid
    Remarks: View Work Orders through the Multiassetlocci table on
    the Asset record
    Object: MULTIASSETLOCCI
    On the Indexes tab/Indexes section:
    Index: MULTIASSETLOC_NDX3
    Table: MULTIASSETLOCCI
    In the Columns for MULTIASSETLOC_NDX3 section:
    Column: Sequence: Ascending?:
    ASSETNUM 1 checked
    SITEID 2 checked
    RECORDCLASS 3 checked
    RECORDKEY 4 checked
    The summary is that there is a need to have Indexes added to
    the MULTIASSETLOCCI table to support queries from an ASSETNUM
    or LOCATION key perspective for databases that have a large
    number of rows in the WORKORDER and MULTIASSETLOCCI tables.
    STEPS TO REPRODUCE:
    *General condition as described
    -Log in to maxdemo instance
    -Go To Work Orders | Work Order Tracking
    -Available Queries | All Records
    -Click to open any record
    *the record must include at least one row in the Multiple
    Assets, Locations and CIs table, and the row must have at least
    one Work Order associated to it
    -Expand the details for the Asset or Location in the Multiple
    Assets, Locations and CIs table
    -In the Asset or Location field | Detail Menu | View Work
    Details
    RESULT:
    Slow performance and timeout is likely when rows are being
    returned
    EXPECTED RESULT:
    The User should be able to view Work Orders as expected from
    the Multiple Assets, Locations and CIs table in the application
    REPORTED IN VERSION:
    Tivoli's process automation engine 7.6.1.1-IFIX20200421-0944
    

Local fix

  • Configure Relationship and Index as described above
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of Work Order Tracking                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * SLOW PERFORMANCE OR TIMEOUT WHEN VIEWING ASSOCIATED WORK     *
    * ORDERS IN MULTIASSETLOCCI TABLE FOR ASSET ON A WORK ORDER    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package:
    	  Release 7.6.1.3 of Base Services
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ24790

  • Reported component name

    MAXIMO ASST MGM

  • Reported component ID

    5724R46AM

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-05-06

  • Closed date

    2020-10-05

  • Last modified date

    2020-10-05

  • 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

    MAXIMO ASST MGM

  • Fixed component ID

    5724R46AM

Applicable component levels

[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761"}]

Document Information

Modified date:
06 October 2020