IBM Support

IJ49448: PERFORMANCE ISSUE IN MAXIMO SCHEDULER

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: Queries executed against scheduler objects were
    taking too long to execute which was causing performance issue.
    
    STEPS TO REPRODUCE:
    ==================
    During the analysis it was observed below mentioned long running
    queries were causing the performance issue.
    
    TIME   #   TEXT
    4199313499 499 select * from skdopascpsalert  where
    skdodmerunid= 68069 for read only
    
    3252633499 499 select * from skdopascpsconflict  where
    skdodmerunid= 68069 for read only
    
    1707612204 204 select * from skdopascpsalert  where
    skdodmerunid= 68078 for read only
    
    1348532204 204 select * from skdopascpsconflict  where
    skdodmerunid= 68078 for read only
    
    132361 14  14 select * from skdopascpsalert  where
    skdodmerunid= 68094 for read only
    
    97557 14  14 select * from skdopascpsconflict  where
    skdodmerunid= 68094 for read only
    
    72006 10  10 select * from skdopascpsalert  where skdodmerunid=
    68098 for read only
    
    56966  9   9 select * from skdopascpsconflict  where
    skdodmerunid= 68098 for read only
    
    34066  4   4 select * from skdopascpsalert  where skdodmerunid=
    68099 for read only
    
    25410  3   3 select * from skdopascpsalert  where skdodmerunid=
    68095 for read only
    
    23971  3   3 select * from skdopascpsalert  where skdodmerunid=
    68096 for read only
    
    20236  3   3 select * from skdopascpsconflict  where
    skdodmerunid= 68095 for read only
    
    19274  3   3 select * from skdopascpsconflict  where
    skdodmerunid= 68096 for read only
    
    17921  2   2 select * from skdopascpsalert  where skdodmerunid=
    68097 for read only
    
    
    In order to improve the performance follow the below steps:
    1) Navigate to System Configuration --> Platform Configuration
    --> Database Configuration.
    2) Filter by SKDOPASCPSCONFLICT, Click on Indexes Tab.
    3) Create New Index and add skdodmerunid in the column section.
    4) Save
    5) Filter for SKDOPASCPSALERT, Click on Indexes Tab.
    6) Create New Index and add skdodmerunid in the column section.
    7) Save
    8) Apply the configuration.
    
    RESULT:
    Before the index creation time taken to execute the query on
    SKDOPASCPSCONFLICT and SKDOPASCPSALERT is more.
    
    EXPECTED RESULT:
    Queries on SKDOPASCPSCONFLICT and SKDOPASCPSALERT should get
    executed faster.
    
    Customer Product Version #
    ========================
    Tivoli's process automation engine 7.6.1.2
    

Local fix

  • In order to improve the performance follow the below steps:
    1) Navigate to System Configuration --> Platform Configuration
    --> Database Configuration.
    2) Filter by SKDOPASCPSCONFLICT, Click on Indexes Tab.
    3) Create New Index and add skdodmerunid in the column section.
    4) Save
    5) Filter for SKDOPASCPSALERT, Click on Indexes Tab.
    6) Create New Index and add skdodmerunid in the column section.
    7) Save
    8) Apply the configuration.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Scheduler users                                              *
    ****************************************************************
    

Problem conclusion

  • A fix for this APAR will be included in a future release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ49448

  • 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

    2023-12-06

  • Closed date

    2024-01-19

  • Last modified date

    2024-01-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

    MAXIMO ASST MGM

  • Fixed component ID

    5724R46AM

Applicable component levels

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

Document Information

Modified date:
19 January 2024