Principal trace log files

Table 46 contains locations, file names, and descriptions of trace logs that can help determine the source of problems with agents.

Table 46. Trace log files for troubleshooting agents
System where log is located File name and path Description
On the Tivoli Enterprise Monitoring Server

  • On Windows: The file in the install_dir\InstallITM path.
  • On UNIX: The candle_installation.log file in the install_dir/logs path.
 Provides details about products that are installed.
Note:
Trace logging is enabled by default. A configuration step is not required to enable this tracing.
The Warehouse_Configuration.log file is located in the following path on Windows: install_dir\InstallITM. On UNIX, the file is located in the following path: install_dir/Install Provides details about the configuration of data warehousing for historical reporting.
The name of the RAS log file is as follows:
  • On Windows: install_dir\logs\hostname_ms_HEXtimestamp-nn.log
  • On UNIX: install_dir/logs/hostname_ms_timestamp.log
Note:
File names for RAS1 logs include a hexadecimal time stamp.

Also on UNIX, a log with a decimal time stamp is provided: hostname_productcode_timestamp.log and hostname_productcode_timestamp.pidnnnnn in the install_dir/logs path, where nnnnn is the process ID number.

 Traces activity on the monitoring server.
On the Tivoli Enterprise Portal Server The name of the RAS log file is as follows:
  • On Windows: install_dir\logs\hostname_cq_timestamp-nn.log
  • On UNIX: install_dir/logs/hostname_cq_timestamp-nn.log
Note:
File names for RAS1 logs include a hexadecimal time stamp.

Also on UNIX, a log with a decimal time stamp is provided: hostname_productcode_timestamp.log and hostname_productcode_ timestamp.pidnnnnn in the install_dir/logs path, where nnnnn is the process ID number.

 Traces activity on the portal server.
The teps_odbc.log file is located in the following path on Windows:install_dir\InstallITM path. On UNIX, the file is located in the following path: install_dir/logs When you enable historical reporting, this log file traces the status of the warehouse proxy agent.
On the computer that hosts the monitoring agent The RAS1 log files are named hostname_productcode_[instance_]timestamp-nn.log and are located in the install_dir\tmaitm6\logs path.
Note:
File names for RAS1 logs include a hexadecimal time stamp.
Note:
Multi-instance agents include the instance ID in the log file name.
 Traces activity of the monitoring agent.
On the computer that hosts the monitoring agent that includes JDBC or JMX data sources The JMX, JDBC, or JAVA log file is named as follows, depending on whether the agent uses JMX, JDBC, or both JMX and JDBC (JAVA):
  • For a single instance agent 
    KXX_JMX|JDBC|JAVA_trace.log
  • For a multiple instance agent 
    KXX_JMX|JDBC|JAVA_instanceName_trace.log
 Traces activity of the data provider JAVA process for JMX, JDBC, or both.

Definitions of variables:

  • timestamp is time stamp whose format includes year (y), month (m), day (d), hour (h), and minute (m), as follows: yyyymmdd hhmm
  • HEXtimestamp is a hexadecimal representation of the time at which the process was started.
  • install_dir represents the directory path where you installed the IBM Tivoli Monitoring component. install_dir can represent a path on the computer that host the monitoring system, the monitoring agent, or the portal.
  • instance refers to the name of the database instance that you are monitoring.
  • hostname refers to the name of the computer on which the IBM Tivoli Monitoring component runs.
  • nn represents the circular sequence in which logs are rotated. Ranges from 1-5, by default, though the first is always retained, because it includes configuration parameters.

See the IBM Tivoli Monitoring Installation and Setup Guide for more information about the complete set of trace logs that are maintained on the monitoring server.