Back ForwardTroubleshooting — Reports and charts

Troubleshooting topics

Various conditions can prevent reports and charts from presenting the expected results.

Show all 

1. Report presents all zeros or no records selected.

Diagnosis

Actions

A report intended to present information about work objects, contains no selected data (or all counts are zero), but the objects for the report were created earlier.

Make sure that the correct application appears in the Application Selector.

Make sure that the Operator ID provides access to the RuleSet versions that make up the application.

Use the Class Explorer to confirm that instances of the work classes exist.

Review class group data instances and the corresponding Database Table instances to confirm that the work objects are mapped to the pc_work table (or to another table with similar columns). 

2. Report fails with Oracle or SQL errors.

Diagnosis

Actions

Oracle or SQL errors arise when a user attempts to execute a report.

Make sure that the correct application appears in the Application Selector.

Review class group data instances and the corresponding Database Table instances to confirm that the work objects are mapped to the pc_work table (or to another table with similar columns).

Using the Class Explorer, review a few work objects in the application; confirm that they all have a common owner organization.

3. "Not a database column" error reported.

Diagnosis

Actions

A report fails with a message "Not a database column."

Make sure that the correct work pool appears in the work pool selector.

Review class group data instances and the corresponding database table instances to confirm that the work objects are mapped to the pc_work table (or to another table with similar columns). SR-768

Open and save the list view rule or summary view rule to confirm that all properties that must be exposed as columns are so exposed.

See Troubleshooting — Property not a database column.

2. Report fails with Oracle or SQL errors.

Diagnosis

Actions

Oracle or SQL errors arise when a user attempts to execute a report.

Make sure that the correct application appears in the work pool selector before running the report.

Review class group data instances and the corresponding database table instances to confirm that the work objects are mapped to the pc_work table (or to another table with similar columns).

Using the Class Explorer, review a few work objects in the application; confirm that they all have a common owner organization.

4. Cannot render image charts

Diagnosis

Actions

Cannot render image charts, server is based on UNIX and lacks Java component AWT

Add the option

-Djava.awt.headless=true

to the JAVA_OPTS line in the setenv.bat file, and restart the system. B-18753 rejected KARAF 7/13/06 also SR-7664 and SR-7496

On UNIX systems with no X11 display confirm that the third-party JAR files pja.jar and pjatools.jar (from eTeks.com) for Pure Java AWT are available to the server. SR-3261 See Pega Developer Network article PDNPRKB-12461 Troubleshooting: Use Pure Java AWT on UNIX hosts to enable chart displays

5. You are not authorized to run this view

Diagnosis

Action

The user attempted to run a list view or summary view report but the Access of Role to Objects rules for the user do not allow access to the objects to be reported on.

Open the access group for the Operator ID of the user to identify the access roles it provides (on the Layout tab).

Identify the Applies To key part of the list view or summary view report.

Find the Access of Role to Object rule that has the access role as a first key part and the class (or a parent class) as second key part.

Review the Search Instances and Execute Activities fields on this Access of Role to Object rule. Update the rule to enable these operations, or create an additional Access of Role to Object rule that conveys these operations.

Related topics How to address advanced reporting requirements
Working with the PegaRULES database

Up Troubleshooting