Transaction Tracking troubleshooting
Check here first if you encounter problems using Transaction Tracking.
- Troubleshooting the Transaction Tracking installation and configuration
If you are experiencing difficulties after installing Transaction Tracking, review this section first to help you resolve any problems. - Transaction Tracking installer fails on SELinux systems
The problem: The Transaction Tracking installer or agent commands fail to run on security enhanced Linux systems - Transaction Collector does not start
The problem: The Transaction Collector fails to start or quits shortly after it has started with an error message TU agent fails to start. - No topology showing in the Transaction Reporter
The problem: After installing SDA, there are problems in the Tivoli Enterprise Portal for Transaction Tracking. - Names in the Transaction Reporter are not displayed correctly
The problem: Names in the Transaction Reporter are not displayed correctly in the Tivoli Enterprise Portal browser. - Historical data is not displayed
The problem: Historical data is not displayed in the Tivoli Enterprise Portal. - Transaction Reporter historical workspaces are not displayed
The problem: Transaction Reporter historical workspaces are not displayed when the Tivoli Data Warehouse is not running. - Data missing when using a single Transaction Collector
The problem: Events are dropped because of synchronization or performance problems: - Data missing when using multiple Transaction Collectors
The problem: The time for the Transaction Collectors is not synchronized, resulting in data from the Transaction Collector that is ahead of time overshadowing data from the Transaction Collectors that are behind time. Data may either not be displayed or not be collected if the cache period is also wrong. - Data from one Aggregation agent is missing from the Transaction Reporter
The problem: Both the Transaction Collector and Web Response Time Aggregation agents are installed, but the Transaction Reporter is ignoring data from one of them. - 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. - Topology is not displayed
The problem: May occur if the topology viewer is not initialized properly in the Tivoli Enterprise Portal Server. - Only partial topology is displayed when using multiple Transaction Collectors
The problem: When using multiple Transaction Collectors, only a partial topology is displayed initially, but eventually the whole topology is displayed. - Topology view missing from Transaction Instances workspaces
The problem: The topology view on the Transaction Instances workspace may be blank if the workspace query for an instance topology times out. A time out can occur when the topology is very large and requires longer than 20 seconds to trace. - Transaction Tracking workspace links are missing
The problem: After using the topology for some hours and refreshing regularly the links in the topology are now missing. - Instances are missing from Transaction Instances workspaces
The problem: After viewing an instance workspace where the initial instances are displayed, subsequent instances for that 5 minute period (by default) are not shown in the workspace. - Metrics are missing from the Transaction Instances table
The problem: In the Transaction Instances workspace, columns added to the Transaction Instances table, such as Processing Time Deviation and Processing Time Baseline, using the Edit Properties window are not displayed in the table. - Transaction instance data is collected even when CollectInstance=false
The problem: The link to Transaction Instance still displays data, even though the profile.xml file was set to CollectInstance=false. - Transaction Collector is not listening
The problem: Transaction Collector is not receiving data - Aggregates are not generated
The problem: Events are arriving at the Transaction Collector but aggregates are not being generated. - External data collectors are not sending data
The problem: The Transaction Collector is not receiving any data from ARM and other external data collectors such as MQ. - Transaction Reporter unable to retrieve aggregates or instances from a Transaction Collector
The problem: Transaction Reporter unable to retrieve aggregates and instances from the Transaction Collector. - Cannot send data to a remote Transaction Collector
The problem: A sample armconfig.xml file is missing from the tusupport directory after installing the Transaction Collector. - Transaction Collector doesn't restart immediately
The problem: When the Transaction Collector is stopped and restarted, for example, using the command ./itmcmd agent stop tu followed by ./itmcmd agent start tu, it may not restart immediately. - Cannot start or stop Transaction Collector or Transaction Reporter remotely on UNIX systems
The problem: This occurs when agents are deployed using different users. - Agent process still running after uninstalling a Transaction Collector or Transaction Reporter remotely
The problem: When uninstalling a Transaction Collector or Transaction Reporter running on UNIX systems remotely, the agent process might not stop automatically. - Tables exported from Transaction Reporter workspaces show unexpected values
The problem: Data exported from a Transaction Reporter flexible context table to a file may show the Java ’long’ variable MIN_VALUE. - FileNotFoundException errors occur when configuring Transaction Collector and Transaction Reporter on Solaris systems
The problem: Transaction Collector and Transaction Reporter were not installed by the same user as the operating system agent, so the files in /var/tmp/plugin_tmp cannot be accessed. - SQL errors in the Historical Transaction Instances workspace
The problem: Tables in the Historical Transaction Instances workspace do not show any data but instead show errors in the information bars. - KCIIN0198E unable to start agent
The problem: Unable to start CICS TXSeries Data Collector on AIX 6.1.4.0 systems. - MQ nodes are not displayed
The problem: MQ nodes do not appear in workspaces. - MQ API exits do not load
The problem: MQ API exits do not load on WebSphere MQ V5.3 for HP-UX. - MQ exits cannot be used by all users
The problem: Not all users accessing the queue manager have the required permissions to access the installed MQ Tracking exits and dependent files. As a result, the queue manager does not work with the exits configured, or there is no activity in the workspaces for the queue manager. - MQ AAT data collector doesn't receive data from MQ queue managers after restarting
The problem: If MQ AAT data collector fails to shut down both the Tivoli Enterprise Management Agent and the data collector, the AAT connection to the MQ queue manager is maintained. When the MQ AAT data collector is restarted, a new instance of the data collector is started.
Parent topic: Transaction Tracking troubleshooting