IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Manage historical data

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

---

Collect Agent Operations Log history

The Agent Operations Log collects the messages occurring on the distributed agents in the enterprise. This log is part of the Tivoli Management Services agent framework. On Windows, if your historical data collection configuration includes the Agent Operations Log attribute group (OPLOG table), you must create directories for the historical data and edit each agent configuration file.

You must manually create history data directories for all agents that are collecting historical data on the same computer and then edit each agent configuration file on the same computer to specify the new path for short-term data collection. This is required on Windows because all agent logs by default are stored in the same install_dir\tmaitm6\logs\ directory and each agent creates an agent operations log file named OPLOG to store short term history data. Thus, the same OPLOG history file is being shared by all the agents; if more than one agent process attempts to warehouse history data from the same short term history binary file, the same data could get transferred to the Tivoli Data Warehouse more than once. For example, the Windows OS and Active Directory monitoring agents are installed. Each process will create and store its operations log history data in a file named C:\IBM\ITM\TMAITM6\logs\OPLOG Now there are at least two processes attempting to share the same history data file. The data from multiple agents can be written to the same file, but the warehouse upload process will encounter problems with this setup. One agent process is not aware that, at any given time, another agent process might be performing the same warehouse data upload from the same short-term history file. This can lead to duplicate history data transferred to the warehouse database.

For each agent that collects historical data on Windows, complete these steps:

Procedure

1. Create a history child directory of install_dir\tmaitm6\logs\.

2. Create a k?? child directory of install_dir\tmaitm6\logs\history where ?? is the two-character product code. For example, c:\ibm\itm\tmaitm6\logs\history\k3z would be the path to IBM Tivoli Monitoring Agent for Active Directory short-term history files. The system user ID for this agent must have read and write permission for this directory.

3. Open the install_dir\tmaitm6\k??cma.ini agent configuration file (where ?? is the two-character product code) in a text editor. See your monitoring product user's guide for the name of the file used for agent configuration.

4. Locate the CTIRA_HIST_DIR=@LogPath@ parameter and append with \history\k?? (where ?? is the two-character product code). For example, CTIRA_HIST_DIR=@LogPath@\history\knt specifies c:\ibm\itm\tmaitm6\logs\history\knt for Windows OS agent historical data collection on this computer.

5. Save the k??cma.ini configuration file.

6. Copy the install_dir\tmaitm6\logs\khdexp.cfg warehouse upload status file to the \history\k?? directory. If this file is not copied to the new agent history directory, your existing history data might be warehoused more than once. It is possible that this file does not exist if the history warehousing option has never been enabled.

7. Copy any .hdr files and their base name counterparts (no file extension) for the agent to the new location. For example, the c:\ibm\itm\tmaitm6\logs\history\knt directory might look like this:

   khdexp.cfg
   netwrkin
   netwrkin.hdr
   ntprocssr
   ntprocssr.hdr
   wtlogcldsk
   wtlogcldsk.hdr
   wtmemory
   wtmemory.hdr
   wtphysdsk
   wtphysdsk.hdr
   wtserver
   wtserver.hdr
   wtsystem
   wtsystem.hdr

   Please note that you might be copying history data files from the tmaitm6\logs directory that are not managed by the target agent. For example, the directory might contain Oracle database history data, but you are copying the files to the new Windows OS agent history directory. The copied files that are not used by the Windows OS agent will not be needed and can safely be deleted.

8. In Manage Tivoli Enterprise Monitoring Services, right-click the monitoring agent service and click Reconfigure, click OK twice to accept the settings in the configuration windows, then Start the agent.

Parent topic:

Manage historical data

---

+

Search Tips   |   Advanced Search