Troubleshooting report issues

This topic describes problems that you might encounter when working with reports.

• Data not appearing in reports
• Latest data not appearing in reports due to cached values
• Error when modifying reports
• Exceeding browsing URL character limits causes issues with report links
• Exceeding the Excel file size limit for exporting causes the export to fail
• Graphs not appearing in reports
• Null exception occurs while opening a graphical report
• Issues with placeholders when sending or scheduling reports
• ORA-00936: missing expression error occurs when using subqueries as a result in another query filter

Data not appearing in reports

If some data is not appearing in reports, you might not have been granted access to the associated domain in BMC Database Automation.

Solution

1. Ensure that you have access to the domain in BMC Database Automation.
    For more information about assigning roles in BMC Database Automation, see Roles in the BMC Database Automation documentation.
2. On the BMC Database Automation Manager, run the run_export script manually, as described in Scheduling-data-export-to-the-data-warehouse-database in the BMC Database Automation documentation.
3. Run the URG Mapper task. For more information, see Providing-credentials-for-Windows-scheduled-tasks.

Latest data not appearing in reports due to cached values

Sometimes, due to cached values, prompt filters do not show the latest values.

Solution

• Click the Refresh values button see the latest values.
• Close the report, log out, log on again, and run the report again.

Error when modifying reports

If you see the following error message when modifying a report, you need to install Java SE 6, update 19 on the computer on which you are trying to modify reports.

Solution

To install Java SE 6, update 19 on the application server, use one of the following procedures:

• Click the Java Virtual Machine link in the error message to download the required Java SE product.
• Download Java SE 6, update 19 from the internet.

Exceeding browsing URL character limits causes issues with report links

Browsers have URL size limitations. When selecting report prompt values, you might exceed the URL character limit. In that case, the links in the report do not display the expected results.

Solution

Determine the URL character length limit for your browser type and avoid exceeding that limit when selecting prompt values.

Exceeding the Excel file size limit for exporting causes the export to fail

If the number of records in a report causes the Microsoft Excel file size to exceed 10 MB, the export to Excel action fails and the browser stops responding.

This is a browser performance issue.

Solution

Close the browser windows, and rerun the report by using more filters to limit the number of records in the report so that the Excel file size does not exceed 10 MB.

Graphs not appearing in reports

Sometimes a graph does not appear in a report (a red X appears in its place).

Solution

The system administrator needs to restart the Adaptive Processing server by using the following procedure:

1. Access the Central Management Console as described in Accessing-the-Central-Management-Console.
2. Select Servers from the drop-down list and click the Servers list.
3. Locate the server that has AdaptiveProcessingServer in its name, right-click it, and select Restart Server.

Null exception occurs while opening a graphical report

In certain instances, a null exception occurs while you attempt to open a graphical report. This behavior is intermittent.

Solution

Restart the BusinessObjects services and try to open the report again.

Issues with placeholders when sending or scheduling reports

When scheduling or sending reports in the BusinessObjects BI platform, if you do not have a correct user account associated with the %SI_EMAIL_ADDRESS% placeholder and you use this placeholder, you encounter issues. A correct account includes a full user name and/or email address.

You might have used a placeholder instead of manually entering an email address in the Destinations dialog box (when scheduling) or Send dialog box (when sending).

If the user account associated with the %SI_EMAIL_ADDRESS% placeholder does not have correct account set up in the Central Management Server database, you might encounter the following issues:

• If you use the %SI_EMAIL_ADDRESS% placeholder in the To or CC field, the report email is not delivered.
• If you use the %SI_EMAIL_ADDRESS% placeholder in the From field, the report email is delivered, but the From field is empty.
• If you use the %SI_EMAIL_ADDRESS% placeholder in the Message field, the report email is delivered, but in the message area %SI_EMAIL_ADDRESS% is displayed literally, instead of the sending user's email address.

Solution

Ask the administrator to access your user account in the Central Management Console as described in Accessing-users-and-groups-in-the-Central-Management-Console and update the account with your full name and email address. 

To temporarily avoid the issue when scheduling or sending a report, insert the actual email address instead of using a placeholder.

For more information about scheduling reports, see Scheduling-reports.

For more information about sending reports, see Sending-reports.

For more information about using placeholders, see the SAP BusinessObjects administration documentation (SAP-BusinessObjects-BI-platform-documentation).

ORA-00936: missing expression error occurs when using subqueries as a result in another query filter

While creating an adhoc report, if you use the result of a query as a value in another query filter, the following error message appears: ORA-00936: missing expression.

Workaround

By default, when creating a custom query, BusinessObjects BI creates an alias for the result of the subquery (for example, @dpvalue('D', DP0.DO215)). To resolve the issue, replace the alias with the exact subquery.