Skip Headers
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for Linux Itanium
  Go To Documentation Library
Go To Product List
Solution Area
Go To Table Of Contents


18 Oracle Reports

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


  • Refer to the Oracle Reports 10g page on OTN, ( for information about Oracle Reports, including a link to download the latest version of the Oracle Reports online Help

  • Your Oracle Application Server software ships with a standalone installation of Oracle Application Server Forms and Reports Services. Use this CD if you do not need all the functionality of the full Oracle Application Server installation. For more information, refer to the Oracle Application Server Forms and Reports Services Installation Guide, available on your Documentation CD. Refer also to the Oracle Reports Technical FAQ on OTN ( for frequently asked questions about OracleAS Forms and Reports Services installation.

18.1 General Issues and Workarounds

This section describes general issues and their workarounds for Oracle Reports. It includes the following topics:

18.1.1 Using the New Auto Save Feature in Reports Builder

Oracle Reports 10g Release 2 (10.1.2) introduces the Auto Save feature, which recovers unsaved changes in the case of an unexpected event of Reports Builder or system fail. When Auto Save is enabled, Reports Builder can automatically recover unsaved changes in open reports.

To enable the Auto Save functionality, you must perform the following steps:

  1. In Reports Builder, select Edit, and then select Preferences to display the Preferences dialog box.

  2. In the Preferences dialog box, on the General tab, select Auto Save.

Alternatively, you can enable the Auto Save functionality by modifying the Reports.auto_save property in the preferences file, cauprefs.ora for Windows prefs.ora for UNIX platforms. Modify the file as follows:

Reports.auto_save = [YES|NO]

Usage Notes

  • When Auto Save is enabled, any modifications done in the reports that are open are saved automatically in temporary recovery files at various events originating from menu, toolbar, tool palette, object navigator, property inspector, and other editor windows in Reports Builder.

  • For a new report definition, Auto Save is enabled only after the report is saved the first time.

  • After you save your report, Reports Builder deletes the current recovery file. Even if you just recovered unsaved changes, Reports Builder deletes the recovery file when you save the report.

  • The temporary recovery file is created and saved in .rdf format in the same location as that of the original definition file. The format of recovery files is reportname_extension.rdf. For example, the recovery file of an original definition file, emp.jsp, would be emp_jsp.rdf. The emp_jsp.rdf file is saved in the same location as the emp.jsp file.

  • If you reopen a previously unsaved report definition file for which a recovery file exists, then Reports Builder prompts you to save the changes. The recovery file contains the changes made until the last Auto Save event. After the changes are recovered, you must select the Save or Revert option. The Save option writes the unsaved previous changes to the original report definition file. The Revert option does not save the recovered changes. Reports Builder deletes the recovery file when you close the report.

  • If an error occurs when autosaving the recovery file, then Reports Builder prompts you to disable Auto Save or continue with the error.


When Auto Save is enabled, Reports Builder assumes that the recovery file contains changes made since the last save of the report definition file. Before you choose to save the recovery file, you must ensure that the recovery file contains your latest changes. If the original report definition file is a later version than the recovery file, then you can choose to revert to the original report definition, so that you do not overwrite it with the changes read from the recovery file.

18.1.2 OracleAS Reports Services Demos Will Not Work If JServ Is Configured

To run OracleAS Reports Services demos successfully, do not configure Apache JServ on the computer where OracleAS Reports Services is installed.

18.1.3 Error While Editing Batch Registered Report in OracleAS Portal

If you batch register a report in OracleAS Portal, then subsequently manually edit the report's registration in OracleAS Portal, you may encounter an unexpected Save As dialog box during the manual editing process.

To work around this issue, specify the Display Name property while editing the report's registration in OracleAS Portal.

Refer to the Oracle Application Server Reports Services Publishing Reports to the Web manual for information on how to register a report with OracleAS Portal.

18.1.4 Limitation on Linked Queries for DelimitedData Output

DelimitedData output does not allow multiple queries to be linked to the main query, because sibling groups are not supported.

For example:

Case 1: You have a link between Q1 and Q2, a link between Q2 and Q3, and a standalone Q4 query.

Q1<-->Q2<-->Q3 Q4

In this case, DelimitedData output is generated correctly.

Case 2: You have a link between Q1 and Q2, a link between Q2 and Q3, and a link between Q4 and Q1.

Q1<-->Q2<-->Q3 Q1<-->Q4

In this case, DelimitedData output is not generated correctly. Alternatively, you can use XML output.

18.1.5 Summary Column Not Aligned for JSP-Based Web Reports with Group Above and Matrix Style

If any summary column values are not correctly left-aligned in the output of JSP-based Web reports with a Group Above or Matrix style, you can implement the following workaround to get proper alignment:

  • Open the JSP report in Reports Builder.

  • Select the Web Source view.

  • In the Web Source view, locate the section where the summary column is defined, and delete the following line to remove the extra space:

    <th class="summary_column_name"> </th>

18.1.6 Images in HTML Output of Oracle Reports Not Displayed When Viewed from Oracle Enterprise Manager 10g

If OracleAS Web Cache is configured as SSL-enabled and Oracle HTTP Server is not, then the images in the HTML output of Oracle Reports is not displayed when viewed from Oracle Enterprise Manager 10g. This is because the image URLs mentioned in the HTML output points to OracleAS Web Cache ports, which are SSL-enabled, whereas the request for past job outputs of Oracle Reports from Oracle Enterprise Manager 10g is non-SSL.

To work around this issue, edit the Servlet property of the URL in the targets.xml file for Reports Server type such that it points to the OracleAS Web Cache port instead of the Oracle HTTP Server port. The targets.xml file is available at ORACLE_HOME/sysman/emd directory.

For example, if your OracleAS Web Cache is SSL-enabled and the listening port number is 443, then the Servlet property of the URL for the Reports Server target in the targets.xml file should be as shown in the following example:

<Target TYPE="oracle_repserv" …..>
<Property NAME="Servlet" VALUE=""/>

18.1.7 Misalignment in Large Multibyte Reports When Using the Enhanced Font Subsetting Feature with Acrobat Reader 7.0

If you use Acrobat Reader 7.0 to view multibyte and unicode PDF reports that use enhanced font subsetting feature (default) and the report size is very large, then some of the characters displayed will not be aligned properly.

To work around this issue, you can do either of the following:

  • Set the environment variable REPORTS_ENHANCED_SUBSET to NO to revert to the Type 3 font subsetting implementation used in releases prior to Oracle Reports 10g Release 2 (10.1.2).

  • Use Acrobat Reader 6.0 or earlier.

18.1.8 PL/SQL Compilation Failure When Using SQL Constructs

PL/SQL compilation may fail if you use SQL constructs in your reports and if the following conditions are present:

  • The SQL constructs were introduced in Oracle Database versions after 9.x, for example, ROW_NUMBER().

  • The SQL constructs are used in client side PL/SQL procedures.

To work around this issue, you can do any of the following:

  • Use Oracle Database Release or later.

  • Move those SQL constructs to the server-side stored procedures.

  • Use the SQL constructs within SQL queries directly instead of procedures.

18.1.9 PL/SQLPackage Specification and/or Body Lost When Saving Report As XML

For a report developed in a release prior to Oracle Reports 10g Release 2 (10.1.2) patch 2, you may encounter the following issue when saving the report in XML format: if the report defines a PL/SQL package, the package specification, and sometimes the body, is not saved in the XML report. To resolve this issue, perform either of the following steps:

  • If the RDF exists, regenerate the XML output file using Oracle Reports 10g Release 2 (10.1.2) patch 2 or later.

  • If the RDF does not exist, edit the XML manually to add type="packageSpec" and/or type="packageBody" to the function element, as shown in the following example:

      <function name="a" type="packageSpec">
            PACKAGE a IS
              function lire return date ;
            END a;
      <function name="a" type="packageBody">
            PACKAGE BODY a IS
              function lire return date is
                c2 date;
                  c2 :=sysdate;
                  return c2;
      <function name="cf_1formula" returnType="date">
            function CF_1Formula return Date is
              aa date;
                --aa :=a.lire;

18.1.10 Incorrect Color for Multiline Text in Paper Design View When Inline HTML Tags Are Used

If any of the following conditions are present, then the text in the Paper Design view of Reports Builder may display in an incorrect color:

  • A text object includes multiline text, which wraps beyond the first line.

  • The text object's Contains HTML Tags property is set to Yes.

  • More than one color is applied to different parts of the multiline text.


This issue is shown in the Paper Design view only. The report output in all other output formats show correct colors.

18.1.11 Out of the Box Reports In Process Server Will Not Work with the Demos (Test.rdf)

Out of the box Reports In Process server will not work if you try to run the demos (test.rdf). You will get following error:

REP-3000: Internal error starting Oracle Toolkit

In some of the Oracle Business Intelligence and Oracle Application Server Forms Services installations, OC4J_BI_Forms service keeps restarting frequently after the install. To resolve this issue, you need to perform a post install setup step. Ensure that the DISPLAY environment variable is set correctly in the following configuration file:


For process-type OC4J_BI_Forms, the default DISPLAY entry is as follows:

<variable id="DISPLAY" value="localhost:0"/> 

You need to change the default DISPLAY entry to a computer with a valid X server. For example, to use the X server running on myserver:0.0, you need to change the following:

<variable id="DISPLAY" value="myserver:0.0"/>

After this change, run opmnctl reload and restart the OC4J_BI_Forms instance. One more way to fix this issue is to define a valid DISPLAY value in the $ORACLE_HOME/bin/ script:

DISPLAY=myserver:0.0; export DISPLAY 

18.1.12 Dynamic refcursor Error

Reports that contain a dynamic refcursor may fail with a virtual memory system error. To resolve this issue, contact Oracle Support Services for the specific patch to apply. Patches are available for Linux x86, Solaris 64-bit, and Windows.

18.2 Vendor-Specific Issues and Workarounds

This section describes vendor-specific issues and their workarounds for Oracle Reports. It includes the following topics:

18.2.1 Underlines Do Not Display in HTMLCSS Output in Browser

In HTMLCSS output, underlines may not display in the browser if you use a custom style for a field object and apply both background color and underline as part of the style, as shown in the following example:

.ReportLevel {text-decoration:underline;color:blue; background-color:yellow}

This is a browser limitation. The browser cannot display underlines, with absolute positioning, for the fields that have both underline and background color applied to them.

18.2.2 JSP-Based Web Report with Large Number of Columns Generates JSP Compilation Error

When you run a JSP-based Web report with more than 149 columns, you may encounter the oracle.jsp.provider.JspCompileException error, as shown in the following example:

500 Internal Server Error
OracleJSP: oracle.jsp.provider.JspCompileException: 
6764 code too large for try statement catch( Throwable e)
{18 code too large public void _jspService(HttpServletRequest request, HttpServletResponse response) throws, ServletException}

This occurs due to a limitation in the Java language that does not enable compilation of Java files with large methods.

18.3 Globalization Support Issues and Workarounds

This section describes Globalization Support issues and their workarounds for Oracle Reports. It includes the following topics:

18.3.1 Images Do Not Display Correctly in Turkish Environment

If you are running reports that include images and use advanced imaging in Turkish environments (when NLS_LANG is set to TURKISH_TURKEY.TR8MSWIN125 or TURKISH_TURKEY.WE8ISO8859P9), then set the environment variable REPORTS_OUTPUTIMAGEFORMAT=[PNG|GIF].

Alternatively, you can control the value in the reports request using the command-line keyword, OUTPUTIMAGEFORMAT=[PNG|GIF}.

18.3.2 MS Mincho Font in PostScript Font Mapping Does Not Work When NLS_LANG is Specified As JA16EUC

When you deploy reports created with Reports Builder on Windows to a Solaris or Linux Reports Server that has NLS_LANG set to JA16EUC, the PDF font mappings will not work. This happens if any one of the following fonts is used in the PostScript font mapping entry:

"<MS Mincho in JP>".....
"<MS PMincho in JP>".....

To work around this issue, you must perform one of the following tasks:

  • Set NLS_LANG to JA16SJIS.

  • Use MS Gothic instead of MS Mincho in PostScript font mappings when creating the reports.

18.3.3 Multibyte Reports Containing Oracle Object Types Hang Report Builder

Reports Builder may stop responding when you run a multibyte report containing an embedded Oracle Object type. This will be fixed in a future patch set.

This is a known issue.

18.3.4 Reports Server's Job Status Messages in Application Server Control Contain Invalid Characters

Oracle Reports status messages on the Job Status page in Application Server Control Console may contain invalid characters if the middle tier character set, NLS_CHARACTERSET (the third field of NLS_LANG) does not correspond to the encoding of the Reports Servlet response for the servlet locale.


The middle tier's default encoding can be different from the Servlet's encoding. For example, when you set LANG to ja or ja_JP.eucJP, the default middle tier system encoding is EUC. However, in this locale, Reports Servlet messages are encoded in Shift_JIS. This is because default encoding for ja_JP is Shift_JIS in the servlet.

Oracle Enterprise Manager 10g converts the messages from the middle tier's NLS_CHARACTERSET to UTF8 resulting in invalid characters in the status messages on the Job Status page. For example, the Reports Servlet messages are encoded in Shift_JIS when the middle tier runs with LANG set to ja and NLS_LANG set to JAPANESE_JAPAN.JA16EUC. However, Oracle Enterprise Manager 10g assumes that the original message is in JA16EUC, and converts it to UTF8, which results in the display of invalid characters in the status messages.

18.3.5 ENVID Ignored While Detecting Duplicate Job

When detecting a new incoming request for a duplicate job where the job request includes the TOLERANCE keyword, Reports Server ignores the value of the ENVID keyword. As a result, the job is marked duplicate of a previous job that was submitted with the same values for all keywords except ENVID.

The following example illustrates this issue:

Report Request Report ENVID TOLERANCE Output
1 Japanese.rdf JA 10 As expected
2 Arabic.rdf UTF 10 As expected
3 Arabic.rdf AR 10 Same as request 2 (incorrect)
4 Japanese.rdf JA 10 Same as request 1 (correct)

In this example, request 4 is correctly marked as a duplicate of request 1 as both the requests use the same values for all keywords, including the ENVID keyword. However, request 3 is incorrectly marked as duplicate of request 2 because both requests use the same values for all keywords, except the ENVID keyword. As a result, the changed ENVID will not be accepted in request 3.To work around this issue, either do not specify TOLERANCE on the command line or specify a dummy user parameter in the job request to differentiate the job requests in duplicate job detection.