|Oracle® Fusion Middleware Release Notes
11g Release 1 (11.1.1) for Linux x86
Part Number E10133-31
This chapter describes issues associated with Oracle Reports. It includes the following topics:
This section describes general issue and workarounds. It includes the following topic:
In Oracle Fusion Middleware 11g Release 1 (126.96.36.199.0) 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
Before installing Oracle Reports 11g Release 1, ensure that the
openmotif22-libs-2.2.4-138.17 library is installed on your machine. If this library is not installed, the installation of Oracle Reports fails.
You can download the library from the following location:
This section lists errors in the Oracle Reports documentation published on OTN. It includes the following topics:
For a matrix report, if the horizontal panels per page is set to a value higher than 1, running the report in the
ENHANCEDSPREADSHEET output format would result in the following error:
REP-1223: THE PAGE SIZE IS INVALID
You can set the horizontal panels per page to a value higher than 1 for a matrix report for all
Note the following corrections to the content in Section 42.5 "Deploy the JSP Parameter Form and the Target Report" of the Oracle Fusion Middleware Oracle Reports User's Guide to Building Reports.
The first paragraph of the section contains the following sentence:
"For testing purposes, however, you can use the Oracle WebLogic Server instance shipped with the Oracle Developer Suite."
Ignore this sentence. The Oracle Developer Suite does not exist in 11g.
Steps 1 and 2 refer to the following as the deployment directory:
This path is incorrect. The following is the correct path:
dir_name is a randomly generated directory name for each deployment instance.