Skip to Content

Troubleshooting report issues

This section contains topics that describe problems that you might encounter when working with reports.

Warning

Note

Many of the corrections described in this section must be performed by the product administrator.

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.

To resolve this process, complete the following steps:

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

Error when modifying reports

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

Cannot Launch Java report panel, you need to install Java virtual machine.

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

  • Click on 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.

Browsers have URL size limitations. When selecting report prompt values, you can create exceed the URL character limit. When this happens the links in the report will not display the expected results.

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 (the browser stops responding).

This is a browser performance issue.

If this problem occurs, close the browser windows, and rerun the report 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

If a graph does not appear in a report (a red X appears in its place), the system administrator needs to restart the Adaptive Processing server using the following procedure:

  1. Access the Central Management Console as described in Accessing-the-Central-Management-Console.
  2. Choose Servers from the drop-down list and then click on the Servers list.
  3. Locate the server with AdaptiveProcessingServer in its name, right-click on it, and choose Restart Server.

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. 

Problems with placeholders when sending or scheduling reports

When scheduling or sending reports in BusinessObjects BI, if you do not have a correct user account associated with the %SI_EMAIL_ADDRESS% placeholder, you will experience problems using the placeholder. A correct account includes a full user name and/or email address.

You might a placeholder instead of manually entering an email address in the Destinations dialog (when scheduling) or Send dialog (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 experience the following problems:

  • 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.

To correct the problem, 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. If you are not an administrator, have your administrator do this.

To temporarily avoid the problem 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. See Additional-SAP-BusinessObjects-Business-Intelligence-platform-documentation for details about accessing SAP documentation.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Decision Support - Database Automation 8.2