> Administrator Guide > Troubleshooting

Administrator Guide

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Troubleshooting

This appendix provides information on troubleshooting problems that occur in Analytics runtime. It includes the following topics:

Note: For details on troubleshooting the installation and configuration of Analytics, see Installation Guide for BEA AquaLogic Analytics.

 

Overview of Logs

The following table provides the descriptions and locations of logs that you can use to troubleshoot Analytics during runtime. Individual log files are generated for each day's activity.

Table A-1 Logs Used to Troubleshoot Analytics in Runtime
Log
Description
Location and Platform
analyticsui.log
Provides activity and error details for the Analytics Console user interface/BEA AL Analytics service.
  • C:\bea\alui\ptanalytics\2.1\logs
    (Windows)
  • /opt/bea/alui/ptanalytics/2.1/logs
    (UNIX/Linux)
wrapper_analyticsui.log
Provides additional activity and error details for the BEA AL Analytics service, including details for these user interfaces:
  • Analytics Console
  • Analytics Administration
  • Analytics Configurator
  • C:\bea\alui\ptanalytics\2.1\logs
    (Windows)
  • /opt/bea/alui/ptanalytics/2.1/logs
    (UNIX/Linux)
asmanagerui.log
Provides activity and error details for the Analytics Administration user interface/BEA AL Analytics service.
  • C:\bea\alui\ptanalytics\2.1\logs
    (Windows)
  • /opt/bea/alui/ptanalytics/2.1/logs
    (UNIX/Linux)
collector.log
Provides activity and error details for:
  • BEA AL Analytics Collector service.
  • Routine partitioning activity that occurs during Analytics runtime.
The partition.log file provides activity and error details for initial partitioning of the Analytics database during upgrade.
  • C:\bea\alui\ptanalytics\2.1\logs
    (Windows)
  • /opt/bea/alui/ptanalytics/2.1/logs
    (UNIX/Linux)
wrapper_collector.log
Provides additional activity and error details for the BEA AL Analytics service, including details for these user interfaces:
  • Analytics Console
  • Analytics Administration
  • Analytics Configurator
  • C:\bea\alui\ptanalytics\2.1\logs
    (Windows)
  • /opt/bea/alui/ptanalytics/2.1/logs
    (UNIX/Linux)
sync.log
Provides activity and error details for Analytics sync jobs.
The sync.log file is located on the Automation Service host machine in the following directories:
  • C:\bea\alui\ptanalytics\2.1\logs
    (Windows)
  • /opt/bea/alui/ptanalytics/2.1/logs
    (UNIX/Linux)

 

Troubleshooting Common Runtime Problems

Table A-2 Common Runtime Problems and Solutions
Problem Description and Details
Cause and Solution
  • Problem: No data is being generated in the report.
  • Details: Analytics reports are not being populated with data.
  • Cause 1: The BEA AL Analytics Collector service is not running.
  • Solution 1: Verify that the BEA AL Analytics Collector service is started. For details, see Installation Guide for BEA AquaLogic Analytics.
 
  • Cause 2: You did not refresh the database views after archiving or restoring partitions.
  • Solution 2: After archiving or restoring partitions, you must refresh the database views by clicking Finish on the Partition Settings page in Analytics Administration.
 
  • Cause 3: You did not correctly configure the analytics-config.xml file.
  • Solution 3: Check your settings in analytics-config.xml and make any necessary changes.
 
  • Cause 4: The fully-qualified domain name is not correctly specified beneath the report-url and admin-rul nodes in the analytics-config.xml file.
  • Solution 4: Correctly specify the fully-qualified domain name beneath the report-url and admin-rul nodes in the analytics-config.xml file.
 
  • Cause 5: The WebLogic Portal host and the Analytics host are not in the same domain.
  • Solution 5: Ensure that the WebLogic Portal host and the Analytics host are in the same domain.
 
  • Cause 6: You did not enter fully-qualified domain names in the analytics-config.xml file.
  • Solution 6: You may have entered host names into the analytics-config.xml file, instead of fully-qualified domain names. Edit the file and replace the host names with fully-qualified domain names.
  • Problem: When using filtering options, reports do not query on all data.
  • Details: Reports only query on data that is associated to properties included in the filter.
  • Example: A company employs 10,000 employees. Only the 200 newest employees are assigned to Departments in their user profiles. The administrator runs a report and queries on a date range, and filters on the Department property, containing the "Human Resources" property value. The report only filters through the 200 newest employees, since only those employees are assigned to a Department. The report does not filter through the other 800 employees, since those employees are not assigned to a Department.
  • Solution: This behavior works as designed. If you want your filtered reports to query on all data, make sure that all data is associated to properties that are included in the filters. Using the example, if you want the report to filter through all 10,000 employees, then you must make sure that all 10,000 employees are assigned to a Department.
  • Problem: The text in Japanese reports does not appear correctly.
  • Details: The Y axis does not display Japanese characters.
  • Cause: The analytics.war file is not configured to display Japanese characters in the Y axis of Analytics reports.
  • Solution: Configure the AnalyticsUIParams.properties file to include font settings that are appropriate to your locale and platform:
  1. Unpack the analytics.war file.
  2. Open the AnalyticsUIParams.properties file for editing. You can find this file in the analyticsui.jar file.
  3. Add these locale entries:
    4. LocaleCode_font_OSName=LocalFont
    LocaleCode_fontSize=14
    LocaleCode_fontSmallSize=10
  4. Save and repackage .war file.
The locale entries should include these values:
  • LocaleCode should include the appropriate two letter language code
  • OSName should include your operating system: Windows, Solaris, or Linux
  • LocalFont should include the name of the font that is appropriate to your locale and platform
Windows example: 
ja_font_Windows=MS PGothic
ja_fontSize=14
ja_fontSmallSize=10

The following table describes common runtime problems and provides solutions to them.


  Back to Top       Previous  Next