Not seeing any defects or statistics and getting ERROR: relation "ts_defects_20130709" does not exist. What can be done to resolve this?

book

Article ID: 48668

calendar_today

Updated On:

Products

APP PERF MANAGEMENT CA Application Performance Management Agent (APM / Wily / Introscope) CUSTOMER EXPERIENCE MANAGER INTROSCOPE

Issue/Introduction

Description:

Not seeing any defects or statistics and getting ERROR: relation "ts_defects_20130709" does not exist. What should be done to resolve this?

Not seeing any defects or statistics which is impacting incidents and reports. On further investigation, it is determined that hourly aggregation is working as expected, but daily/weekly/monthly aggregation is not working.

Various errors are found:

  1. In the Postgres or Oracle Log:
    ERROR: relation "ts_defects_20130709" does not exist at character 13
  2. In the TIM Collector Log:
    [DefectLoginProcessingPool.Thread4][Manager.com.timestock.tess.services.processors.DefectProcessor] Update failed for biz event 13861 org.postgresql.util.PSQLException: ERROR: relation "ts_defects_20130709" does not exist

What can be done to resolve this?

Solution:

In 9.1.4-9.1.6, the Java threadsize was increased. Using the default values are inadequate for successful defect and statistics aggregation. As a result, there will be no defects or statistics on the MOM GUI Reports Interface.

To increase this value and have successful defects/stats aggregation, do the following:

In the tess-default.properties file or tess-customer.properties file (tess-customer.properties overrides tess-default.properties), change -XX:ThreadStackSize to 512 in both fields below:

# do daily stats aggregation in a separate JVM.dailystats.aggregateInSeparateJvm=true
dailystats.jvmArgs= -XX:+CMSClassUnloadingEnabled -XX:+UseConcMarkSweepGC -XX:+UseBiasedLocking -XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=90 -Dlog4j.configuration=log4j.properties -Xms256M -XX:ThreadStackSize=128 (Change to 512)

This change should be made on the EM running Defects Aggregation (the TIM Collector) and Stats Aggregation (The Stats Aggregation Collector)

# do defect aggregation in a separate JVM.
dailystats.aggregateInSeparateJvm=true
defects.jvmArgs= -XX:+CMSClassUnloadingEnabled -XX:+UseConcMarkSweepGC -XX:+UseBiasedLocking -XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=90 -Dlog4j.configuration=log4j.properties -Xms256M -XX:ThreadStackSize=128(Change to 512)

Increasing the ThreadStackSize and restarting the appropriate collector should resolve the defects/statistical aggregation issue.

Notes:

  1. This is fixed in 9.1.7 and later. It is also fixed in 9.5.1 and later.
  2. The SeparateJVM option may not be needed if

    • using a 64 bit JVM with a very large heap or
    • processing low to moderate numbers of statistics

Environment

Release:
Component: APMCEM