TIM Collector is running but I am not seeing defects, statistics, Introscope metrics, etc. What shall I do?

Products

• CA Application Performance Management Agent (APM / Wily / Introscope)
• INTROSCOPE

Issue/Introduction

Description:

This document explains how to recover from the rare condition where the TIM Collector appears to be up but is really hung.

Solution:

It is possible that the TIM Collector is hung, but the RTTM and Transaction Discovery processes appear to be running.

The key is to look at the TIM Collector logs and see if you have the ability to switch Collectors. If the button to do so is grayed out, check the TIM Collector logs for the following Errors:

[ERROR] [ServicesCheck.Thread1] [Manager.com.timestock.tess.services.service.CheckServices] Could not start service 'TIM.Collection.Svc' on entity 25: the service did not stop <---Key Line

If the TIM Collection Service is not running, then the new base tables were not created and daily aggregation is also failing:

[ERROR] [Thread-41] [Manager.com.timestock.tess.services.processors.StatsAggregator] [main] [com.timestock.tess.util.TessLogger] Statement failed '{ call dbms_stats.gather_table_stats(?,?,?,?) }'
java.sql.SQLException: ORA-20000: TS_ST_TS_US_INT_20131104 invalid partition name

Please follow these steps to start the TIM Collection Service:

1. Create a database backup before doing steps 2-4
   
   
2. Stop the Collector running TCS (TIM Collection Service)
   
   
3. Execute the SQL Statement: "UPDATE TS_ENTITY_SERVICE SET TS_LOCKED_BY_ENTITY=TS_ENTITY_ID WHERE TS_LOCKED_BY_ENTITY='0' AND TS_SERVICE_ID='1';"
   
   
4. Restart Collector running the TIM Collection Service

These steps should start the TIM Collection Service and create any missing database partitions.

Daily stats aggregation should run successfully after missing partitions are created.

Environment

Release:
Component: APMCEM