35 views

Description

If several business services (BS) change in one impact calculation, it loads the AlertHistory records for each BS. But if an alert appears in more then one business service, it will load it twice.

The impact job is responsible for calculating all the impact, including calculatong the dashboard (Event management > Dashboard), and the severities on the bs-map (drill down from a group). Disabling the job will keep the impact on dashboard as is, and not change according to new alerts.

Steps to Reproduce

  1. Set impact calculation scheduled jobs.

    For more information, see the product documentation topic Scheduled jobs installed with event management.

    Note that Event Management - Impact Calculation repeatedly turns off and there are OOM issues when running impact calculation.

 

 

Workaround

For a permanent fix, if you are able to upgrade, review the Fixed In field to determine the versions that have a permanent fix.

For a workaround if you cannot upgrade: Set the table cleanup sys_auto_flush for the em_alert_history table to two days instead of a week. Change the Age in seconds setting from 604,800 to 172,800. The Age can be decreased to 1 day (86400 seconds) if the out-of-memory issue still occurs. 

  1. Navigate to Table Cleanup.

  2. Under System Maintenance, go to Table Cleanup, and click New.

  3. Use the following settings:

    Table: em_alert_history

    Age in seconds: 172,800

  4. Click Submit.

 


Related Problem: PRB1057120

Seen In

There is no data to report.

Fixed In

Istanbul Patch 8
Jakarta Patch 2
Kingston

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-04-24 03:37:54
Published:2018-04-02