IBM Tivoli Composite Application Manager for Transactions, Version 7.4.0.0

Transaction Reporter cannot write to short term history file

The problem: When using historical data collection, the short-term history file for the Transaction Reporter, such as to/hist/INTERACTN, becomes very large and the Transaction Reporter cannot write to the file.

The solution: Usually, the Transaction Reporter cannot write to the short term history file because the disk is full or the file has reached its size limit. Contain the size of the short term history file using one of the following methods:
  • Limit the size of the short term history directory for the Transaction Reporter.
  • Reduce the amount of data held in the short term history file by the Tivoli Enterprise Monitoring Server.
To limit the size of the of the short term history directory for the Transaction Reporter:
Attention: Setting the maximum size and time period may cause gaps to appear in the data.
  1. Open the Transaction Reporter configuration file:
    • On Windows systems, CANDLE_HOME\TMAITM6\KTOENV
    • On Linux and UNIX systems, CANDLE_HOME/config/to.ini
  2. Set KHD_TOTAL_HIST_MAXSIZE, which defines the maximum size of the short-term history directory (specify in MB). For example, KHD_TOTAL_HIST_MAXSIZE=1024.
  3. Set KHD_HISTSIZE_EVAL_INTERVAL, which defines the time period in seconds between evaluations of the size of the short-term history directory. For example, KHD_HISTSIZE_EVAL_INTERVAL=900 .
  4. Save and close the file.
When the maximum size of the short term history directory is reached, no further records are written to the file until the warehouse proxy has warehoused the data and reduced the file size.

To reduce the amount of data held in the short term history file by the Tivoli Enterprise Monitoring Server if the Tivoli Enterprise Monitoring Server is the collection location:

  1. Open the Tivoli Enterprise Monitoring Server configuration file:
    • On Windows systems, CANDLE_HOME\CH\cms\KBBENV
    • On Linux and UNIX systems, CANDLE_HOME/CH/config/hostname_ms_TEMSname.config
  2. Set KHD_HISTRETENTION, which defines the number of hours of data to be held in the short-term history file. The default is 24 hours. For example, KHD_HISTRETENTION=1
  3. Save and close the Tivoli Enterprise Monitoring Server configuration file.
  4. Update the KFW_REPORT_TERM_BREAK_POINT environment variable in the Tivoli Enterprise Portal Server configuration file to synchronize the two values.
  5. Synchronize the KHD_HISTRETENTION parameter for all other monitoring agents that use the same Tivoli Enterprise Monitoring Server and Tivoli Enterprise Portal Server.


Last updated: September 2014