32 Oracle Reports

This chapter describes issues associated with Oracle Reports. It includes the following topics:

32.1 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topic:

32.1.1 Mapping Users and Roles to Reports Application

In Oracle Fusion Middleware 11g Release 1 ( installations, roles and users are not added to the Reports application, by default. To run a report using JPS security, you must add roles and users to the Reports application.

For more information, see:

  • "Managing Application Roles" in the Oracle Fusion Middleware Security Guide

  • "Managing Users and Security Policies" in the Oracle Fusion Middleware Publishing Reports to the Web with Oracle Reports Services manual

32.1.2 Configuration Fails While Starting WLS_Reports Server

While starting managed weblogic server, WLS_REPORTS, configuration fails showing the following errors:

The input line is too long.
The syntax of the command is incorrect.

This occurs when user creates MW_HOME, ORACLE_HOME and domain directory with long names. Consequently the value for environment variable like JAVA_OPTIONS and CLASSPATH become very long, and the actual command for starting the WLS_REPORTS Managed Server exceeds the windows command maximum limit of 8191 characters.

To work around this issue, use short names for ORACLE_HOME, MW_HOME and domain directory on windows.

32.1.3 Oracle Reports Builder Fails to Open the Data Model from Object Navigator

On Microsoft Windows x64 (64-Bit) systems, Oracle Reports builder fails to open the Data Model view when you double-click the data model icon from the Object Navigator.


From the File menu, select New, then select Report, and then select the Build a new report manually option to open the Data Model view.