4 Oracle Reports

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

4.1 General Issues and Workarounds

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

4.1.1 Mapping Users and Roles to Reports Application

In Oracle Fusion Middleware 11g Release 2 (11.1.2) 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

4.1.2 Reports Server Failure in Forms and Reports 11gRelease 2 (11.1.2)

Reports Server fails to start after installing and configuring Forms and Reports 11.1.2.

To work around this issue, perform the following steps before you start a Reports Server instance:

  1. Locate the cwallet.sso file at

    domainHome\config\fmwconfig\bootstrap

  2. Add the write permission to the SYSTEM user's assigned privileges.

  3. Restart Reports Server.

    After granting write permission to the file for SYSTEM user, the Reports Server starts.

4.1.3 Rwservlet Diagnostic Output Disabled in Forms and Reports 11g Release 2 (11.1.1.2)

The out-of-the-box setup for rwservlet diagnostic output is disabled for a non-secure Reports Server. In case, the user needs to execute web commands, the webcommandaccess parameter needs to be set. For more information about this parameter, see Intermediate-level Security for Forms and Reports in Oracle Fusion Middleware Publishing Reports to the Web with Oracle Reports Services.