Overview of Logs

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

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-url nodes in the analytics-config.xml file.

Solution 4: Correctly specify the fully-qualified domain name beneath the report-url and admin-url nodes in the analytics-config.xml file.

Cause 5: The WebLogic Portal host and the Oracle WebCenter Analytics host are not in the same domain.

Solution 5: Ensure that the WebLogic Portal host and the Oracle WebCenter 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 Oracle WebCenter Analytics reports.

Solution: Configure the AnalyticsUIParams.properties file to include font settings that are appropriate to your locale and platform:

Unpack the analytics.war file.

Open the AnalyticsUIParams.properties file for editing. You can find this file in the analyticsui.jar file.