IBM Support

Maintaining the MQ Workflow system and error logs at a manageable size

Troubleshooting


Problem

The MQ Workflow system and error logs should be managed to periodically reduce their size so they don't become too large.. The logs are found as system files and database tables.

Symptom

The fmc.system_log and/or fmc.error_log tables grow too large.

Cause

Variables controlling automatic pruning of the tables are not set. Another cause may be due to a faulty process design creating large numbers of FMC22590W and FMC22595W warning messages in a single day.

Diagnosing The Problem

The fmc.system_log and/or fmc.error_log tables may be very large and contain millions of entries..

  • Have your database administrator take a row count of these tables to determine how large they are.
  • If using DB2 the db2diag.log file may contain lock escalations related to these tables. Several thousand escalations would constitute many.
    Example: MESSAGE : ADM5502W The escalation of "510864" locks on table "FMC.SYSTEM_LOG" to lock intent "X" was successful.

Resolving The Problem

  • The corresponding fmcsys.log and fmcerr.log files must be maintained manually.
    1. Periodically they should be deleted or renamed to maintain a manageable size to deal with for troubleshooting.
    2. It is good practice to keep copies of old files for historical purposes in case a new problem requires looking at how the system was operating several months back. MQ Workflow will automatically generate new system and error log files if the originals are deleted or renamed.

[{"Product":{"code":"SSVLA5","label":"WebSphere MQ Workflow"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"System Administration","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"3.6.0.6;3.6;3.5","Edition":"All Editions","Line of Business":{"code":"LOB45","label":"Automation"}}]

Product Synonym

fmc00wf fmc00sya fmc00inc fmc00dba fmc00pds

Document Information

Modified date:
15 June 2018

UID

swg21457557