IBM ITM

STH - Short Term History files

Controlling the number of hours of historical data stored http://www-01.ibm.com/support/docview.wss?uid=swg21263578

HOW HISTORICAL DATA ARE COLLECTED AND PROCESSED

The Warehouse Proxy Agent reads data from binary history files that are collected at the Tivoli Enterprise Management Server (TEMS) or at the Tivoli Enterprise Management Agent (TEMA). These files are sometimes referred to as Short Term History (STH) files. The agent attempts to insert this data into tables in the Tivoli Data Warehouse (TDW). If the data is more than 24 hours old and has been successfully inserted into the Data Warehouse, the data is removed from the binary history files when warehousing occurs. If, for any reason, the insert operation fails, the binary history file continues to grow. Setting the Warehouse Interval to OFF in the History Collection Configuration panel for an attribute group has the same effect: Data in the binary history file is not added to the TDW, and the size of the binary history file continues to grow.

STH Files full - situation

http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?topic=%2Fcom.ibm.itm.doc_6.2.fp1%2Fitm_admin165.htm&path=3_6_0_1_14_5_0

What to do when the short-term history file directory size reaches its limit

When the KHD_TOTAL_HIST_MAXSIZE and KHD_HISTSIZE_EVAL_INTERVAL environment variables have 
been set for the Tivoli Enterprise Monitoring Agent (or at the Tivoli Enterprise 
Monitoring Server if data collection occurs there), no more historical data samples are 
added to the short-term history files if that maximum directory size has been reached.

You need to resolve the cause of the unchecked short-term history file growth before the 
saving of data samples to the history files can resume. When data is collected at the 
agent you can create a custom SQL query or a situation or both that reports when this 
condition occurs.

Here is an example of a custom SQL query that you can run:

SELECT ORIGINNODE, CATEGORY, SEVERITY, TABLE, TIMESTAMP, MESSAGE 
FROM O4SRV.KRAMESG WHERE ORIGINNODE = $NODE$ 

reimport STH files into TDW

However, my friends in ITM support tell me that once you have your WPA running and configured correctly to insert STH into the warehouse, you can stop all agents / ITM processes and then rename the current STH file and replace it with your old STH data file. Run the WPA (TEMS TDW etc) on the file and WPA will warehouse the data normally - Do not run the agent to collect STH while this is going on. After this you could stop everything again then rename the STH history files back to the live ones, restart all ITM components and the agent. If you run summarization and pruning against the warehouse there may be a problem and you would need to review this technote to ensure that works correctly (http://www-01.ibm.com/support/docview.wss?uid=swg21584317).