IBM Support

IBM Enterprise Content Management System Monitor (ECM SM) is not processing New Events

Troubleshooting


Problem

IBM Enterprise Content Management System Monitor (ECM SM) is not processing New Events

Symptom

Events may be displayed in the ECM SM WebConsole, but the Events are not current.

Cause

A possible issue is that a Product being monitored had so many errors reported that ECM SM was unable to keep up with an extremely number of Log entries. This is referred to as an "Event Storm".

Diagnosing The Problem

If after clearing some Events, restarting the ECM SM Server Processes/Services, verifying the Clients have the CALA and CALA_REX Processes/Services running, still the ECM SM Server is still not showing current Events then it may be the results of an Event Storm.

Resolving The Problem

To Clean up processes in case of Event Storm perform the following procedures:

(*** Perform a full Backup (ECM SM and the Database) so you can restore if needed!!!!***)

Follow these procedures and if step 7 is not functional, skip past steps 7, 8, and 9.
(Note: For a reference, the Users Guide contains all the Tables used by ECM SM.)

  1. Collect the entire <ECM SM install>/var/log directory where the server and gui logs are located.
  2. Stop all the Cala processes on each client. (The Cala Clients should be stopped if the ECM SM Server will not be running for some time. Events will back up from each Client.)
    This can be the “Stop CALA” Task run from TEMa (Task Execution Manager).
  3. Examine the blocked_events.txt file.
    Check the hostname reported.
    This would be the possible system causing the Event Storm.
  4. Stop the Cala running on that Host.
  5. Go to that Host (usually a P8 System) and delete all files with a bkf extension.
    (There will be 1 or 2 in the path <ECM SM client install>/cala)
    (If the ECM SM Server has been down for a period of time, this may need to done on all the clients.)
  6. Delete all the files in the Cala Cache. (<ECM SM client install>/cala/.calacache)
  7. Go to the ECM SM Webconsole and then go to the “Database Cleanup Configuration” page.
    Run the “Close Logfile Events older than” tool but break it down into steps. Don't want to run this over an extreme amount of Events. Maybe a month at a time. Set the time interval and click on Run.
  8. When the Logfile is down to two weeks, try starting the Webconsole.
  9. With the Webconsole running, start enabling the Cala on the Clients.
    This can be the “Start CALA” Task run from TEMa.
    If the step 7 not running, continue here...
  10. Perform these steps:
    Backup <ECM SM Server>/server/cfg/finca-cfg.xml.
  11. Open finca-cfg.xml for edit.
    Increase the eventjournal - inqueuemaxsize in
    .../server/cfg/finca-cfg.xml to
    <inqueuemaxsize>1000000</inqueuemaxsize>
    Save the changes and exit from the file.
  12. Restart all of the ECM SM services so these changes will be in effect.
    Do the Events process? If yes, try continuing with step 7 above.
    Otherwise, continue below...
  13. EVT_HIST and EVT_NEW contain a new column ADD_INFO.
    (Table EVTJRN_ADD_INFOS was removed RDB ECM SM FP1.)
    Check the number of entries in the table:
    select count(*) from EVTJRN_EVTS;
    select count(*) from EVT_HIST;
    select count(*) from EVT_NEW;
  14. Stop ECM SM server first. Delete the entries in tables if larger than 200K
  15. Start the ECM SM Server.
  16. Enable Cala on one client.
    If successful, continue enabling the Cala on the other Clients.
    If problems continue, engage IBM Support.

Related Information

[{"Product":{"code":"SSEM9N","label":"Enterprise Content Management System Monitor"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"FileNet System Monitor","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"5.2;5.2.0.1;5.2.0.2","Edition":"All Editions","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 June 2018

UID

swg21975328