Skip Headers

Oracle® Developer Suite Release Notes
10g (9.0.4) for Windows and UNIX
Part No. B10668-01
  Go To Documentation Library
Go To Table Of Contents
Go To Index

Previous Next  

9 Oracle Reports

This chapter discusses issues and workarounds for Oracle Reports, including Oracle Reports Developer (Reports Developer) and Oracle Application Server Reports Services (Reports Services). The chapter includes the following topics:

The notes in this chapter cover issues and workarounds that are not documented in Oracle Reports 10g manuals and online help. For information about the new features in this release, refer to the Oracle Reports 10g page on OTN (, and to the "About this release" topic in the Reports Builder online help.


You can also download the latest version of the Reports Builder online help from the Oracle Reports 10g OTN page.

9.1 General Issues and Workarounds

This section describes general issues and workarounds for Oracle Reports.

9.1.1 FTP and WebDaV Destinations Not Supported from Reports Builder

Currently there is no support for FTP and WebDaV destinations from the Reports Builder environment. However, they are supported from the Reports Runtime and the Reports Server environments.

9.1.2 Oracle9i JDeveloper Integration Deadlock When Debugging JSP Reports in Oracle9i JDeveloper

When you are debugging an OracleAS Reports Services JSP in Oracle9i JDeveloper (JDeveloper), you must disable any breakpoints that are not of source type. If you do not disable these breakpoints, a deadlock occurs. You can disable breakpoints that are not of source type in the Breakpoints window. Graph Not Appearing in Oracle9i JDeveloper

When you run a JSP report with the rw:graph tag in JDeveloper, the graph image is not visible in the browser. To fix this problem, set the IMAGEURL parameter in the file in oracle_home/reports/conf:

oracle.reports.rwclient.RWClient Reports in-process server

If you set the JDeveloper Java Virtual Machine (JVM) to ojvm, minimal, or vanilla (Project Settings > Runner > Virtual Machine), the rwservlet's in-process server is not killed when you terminate JDeveloper’s embedded OC4J server. As a result, a port conflict occurs the next time you start OC4J. To avoid this problem, do one of the following:

  • Set the JVM to hotspot.

  • Disable the in-process server in
    oracle_home/reports/conf/ by setting

  • Use the standalone Reports Server instead.

9.2 Platform-specific Issues and Workarounds

This section contains issues and workarounds that apply to specific operating environment platforms supported by Oracle Developer Suite.

9.2.1 Windows Platform Issues and Workarounds

This section contains issues and workarounds that apply specifically to supported Microsoft Windows platforms. Using osfind with JDK 1.4

Oracle Reports’s architecture uses VisiBroker’s osagent to find the various servers running in the network.

You use osfind to find various osagent instances running on the network. However, osfind does not work with the JDK version used by Oracle Application Server (version 1.4). To work around this issue and find osagent instances running on the network, you must run osfind with the following settings:

osfind -J-Xbootclasspath /p:oracle_home\vbroker4\lib\vbjboot.jar Invoking the Getting Started Page From Reports Builder

If you open the Getting Started page from Reports Builder using Netscape 7.0, you might get a Failed to locate browser error. To correct this problem:

  1. Open the Windows registry using a registry editor (for instance, regedit.exe).


    Create a backup of the registry before proceeding to edit it.

  2. Navigate to the following key:

  3. Delete all other values except Default.

  4. Run Reports Builder and select Getting Started.

  5. Click OK. The Information Navigator Preferences dialog box appears.

  6. Select Netscape Navigator 7.0+ as the browser. Ensure that the path and the browser program name are accurate. To change the browser location (if the path or the program name is incorrect):

    1. Click Browse.

    2. Navigate to the location and program name you want.

    3. Click OK.

  7. In the Information Navigator Preferences dialog box, click OK. Printing Reports Without Hardware-based Left Margins

Oracle Reports 10g (9.0.4) has been changed to generate the report output relative to the top-left corner of the physical paper. Earlier, the printer's printable area was used, causing inconsistencies in the location of the report output when used across different printer models.

If required, you can revert to the earlier behavior by setting the registry key REPORTS_ADD_HWMARGIN to YES.

To set the REPORTS_ADD_HWMARGIN registry key to YES:

  1. Back up the Windows registry, then edit it using a registry editor such as regedit.exe.


    Refer to Windows online help for instructions on how to back up the registry.

  2. Navigate to the key HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE, then find the HOMEn key that contains the directory for the Oracle home that contains Reports.

  3. With this key selected, add a new String sub-key named
    and set its value to YES.

By default, the non-printable left margin of the printer is ignored. The printing origin starts from the top-left corner (0,0) of the physical paper and not the printable area. If you have set the registry key value to YES and then want to switch to the default, you can set the key value to NO, or you can delete the key.

You must provide enough margin in your report's layout to put the data within the printable area. The margin fields in the Page Setup dialog box of Reports Builder have been disabled to ensure consistency with OracleAS Reports Services.

9.2.2 UNIX Platform Issues and Workarounds


UNIX issues are classified as platform-specific unless it is certain that they occur on all UNIX platforms. Also, platform-specific issues are only reported for the platform on which they were first detected; an issue that is listed as "platform-specific" may actually occur on several platforms. Unless the notes say otherwise, you should only use a platform-specific workaround on the stated platform. General UNIX Platform Issues and Workarounds

This section contains issues and workarounds specifically for all supported UNIX platforms including SPARC Solaris, HP HP-UX, and Linux x86. Implementing removal of DISPLAY and printer dependencies

With Oracle Reports 10g (9.0.4), it is no longer necessary to have the DISPLAY environment variable or a valid printer defined at runtime.

The REPORTS_DEFAULT_DISPLAY environment variable specifies whether to implement the following features:

  • The elimination of the dependency on the DISPLAY environment variable, which was required in prior releases to define the windowing system display surface for creating images and getting pixel resolution.

  • The elimination of the dependency on having a valid printer defined for font information (PRINTER and TK_PRINTER environment variables set to a valid printer, or a valid entry in uiprint.txt).

  • Using screenprinter.ppd for surface resolution for images and font information.

  • Enhanced imaging support


  • For existing customers upgrading to Oracle Reports 10g (9.0.4), the default setting (YES) may impact the appearance, number of pages, output file size, or performance of existing reports.

  • Even when the DISPLAY environment variable is set, it will not be used unless REPORTS_DEFAULT_DISPLAY is set to NO.

See Also:

  • Oracle Application Server Reports Services Publishing Reports to the Web and the Reports Builder online help for more information on the REPORTS_DEFAULT_DISPLAY environment variable and screenprinter.ppd.

  • The section "Fonts in Report Output" in the chapter "Managing Fonts in Oracle Reports" in Oracle Application Server Reports Services Publishing Reports to the Web. Solaris Issues and Workarounds


Although these issues were seen on Solaris, they may also exist on other UNIX platforms, such as Linux and HP-UX. Invoking the Graph Wizard in a multibyte environment

On Solaris, invoking the Graph Wizard in a multibyte (Japanese, Simplified Chinese, and Korean) environment causes Reports Developer to stop responding.

To work around this issue, you must:

  1. Install J2SE Version 1.4.2 on your computer. You can download J2SE 1.4.2 from Sun Microsystem’s Java web site (

  2. Set the path to the J2SE home in the file:

    PATH=$J2SEHOME/bin:$ORACLE_HOME/jdk/bin: $ORACLE_HOME/bin:${PATH};export PATH

  3. Modify LD_LIBRARY_PATH in to point to the location of the J2SE home:

    LD_LIBRARY_PATH=$J2SEHOME/lib/sparc: $ORACLE_HOME/jdk/jre/lib/sparc:$ORACLE_HOME/lib: ${LD_LIBRARY_PATH}; export LD_LIBRARY_PATH Linux Issues and Workarounds

This section contains issues and workarounds specifically for supported Linux x86 platforms. Radio box selection using mouse in New Program Unit dialog box does not take effect (3209858)

Reports Builder has a known issue with selecting a radio button with your mouse.

When you select a radio button in the New Program Unit dialog box, close the dialog box (for example, by clicking on Cancel) and then reopen the New Program Unit dialog box, you cannot select the same radio button.

For example, if you select the Function radio button, close the New Program Unit dialog box, and then reopen it, you cannot select the Function radio button.

You can work around this using either of the following methods:

  • Select a radio button other than the one you selected previously, then select the one you want. For example, to select the Function radio button, first select the Procedure radio button. You can then select the Function radio button.

  • Use your keyboard to select the radio button. Navigate to the radio button using the Tab, Up, and Down keys, then use the space bar to select the radio button.

For further details, please refer to bug 3209858: RWBUILDER: NEW PROGRAM UNIT: CANNOT MAKE RADIO BUTTON SELECTION WITH MOUSE HP-UX Issues and Workarounds

There are currently no known HP-UX-specific issues.

9.3 Configuration Issues and Workarounds

This section contains issues and workarounds for Oracle Reports Developer configuration.

9.3.1 Repairing Fonts Not Appearing Correctly in Web Source View

Text in the user interface of Reports Builder, such as the window title, uses fonts taken from the system resource files for the current language. These system resource files are supplied with the Oracle Reports installation. In Oracle Reports, you can map these fonts in the [RWBUILDER] section of uifont.ali. If found, the mapped font is used instead of the original font; if not, Oracle Reports uses the original font.


The mapped font needs to be a fixed-width font.

In the Web Source view of the Report Editor, the following languages may appear garbled: Arabic, Central European languages, Cyrillic, Greek, Hebrew, Japanese, Thai, and Turkish. To work around this issue, you can set the font names for Reports Builder in uifont.ali as follows:

.....AR8MSWIN1256="Courier New"
.....CL8MSWIN1251="Courier New"
.....EE8MSWIN1250="Courier New"
.....EL8MSWIN1253="Courier New"
.....IW8MSWIN1255="Courier New"
.....JA16SJIS="MS Gothic"
.....TH8TISASCII="Andale Duospace WT"
.....TR8MSWIN1254="Courier New"

You can download a copy of the Andale Duospace WT (fixed-width) font from OracleMetalink ( The ARU number is 2638552.

9.3.2 Optimizing the Deployment of Reports

Before you deploy a report on a computer that is either slow or is running on a load, you may want to configure the following:

  • Ping timeout (OPMN-side): Ping timeout is the measure that OPMN uses to determine the time that it must wait for a callback from an in-process Reports Server (in OC4J_BI_FORMS), before considering it as a timeout.

    The default timeout period is 150. This period is calculated from: ping timeout, ping interval, and number of retries. The default values for these are:

    • ping timeout = 30 seconds

    • ping interval = 20 seconds

    • number of retries = 3


    The number of retries is applicable only when OPMN successfully connects to OC4J and receives regular ONS notifications from the process.

    Based on these values, there will be three ping attempts with a timeout of 30 seconds each at 20 second intervals. The first ping is done after the specified ping interval. Thus, from the time the OC4J is started by OPMN, approximately 150 (20 + 3*30 + 2*20) seconds will elapse before the process is considered unresponsive and restarted. However, if after OPMN connects to OC4J but OC4J is too slow in sending regular ONS notifications then the 30 second timeout is applicable.

    See Also:

    Oracle Application Server Reports Services Publishing Reports to the Web for more information on the opmn.xml file.

  • Callback timeout (Reports Server-side): Callback timeout is the measure that Reports Server uses to determine the time that it must wait for a response from the engine before timing out. You can specify this value in the Reports Server configuration file, server_name.conf. This time out period is in milliseconds.

    For example:

    <engine id="rwEng" class="oracle.reports.engine.EngineImpl" initEngine="1"
    maxEngine="1" minEngine="0" engLife="50" maxIdle="30"


    Increase the timeout when the machine is very slow.

9.3.3 Improving Image Resolution of Graphs Displayed in a PDF File or on a Printer

The REPORTS_GRAPH_IMAGE_DPI environment variable specifies a dots per inch (DPI) value for graphs displayed to a PDF file or on a printer. The default value for this environment variable is 72 DPI, which minimizes the time it takes to generate the report and reduces the report file size.

If you specify a value higher than 72 DPI, you will see an improvement in the image resolution. However, this increases the time it takes to generate the report and increases the report file size.

For instance, setting the value to 250:

  • Increases the time to generate a report by 5 to 6 times that of a report generated at 72 DPI.

  • Increases the PDF file size by 5 to 6 times that of a report generated at 72 DPI.

Usage Notes

  • The valid values are 72 through 300.

  • The default value is 72.

  • For Windows, set the value in the Windows registry key
    REPORTS_GRAPH_IMAGE_DPI. Refer to Section, "Printing Reports Without Hardware-based Left Margins" for instructions on how to set a registry key value.

  • For UNIX, set the value by setting the environment variable in

  • When you set a DPI value greater than 250 and your chart is bigger than 5"x5", you may also need to change the JVM heap size value using
    REPORTS_JVM_OPTIONS to avoid an Out Of Memory error in the JVM.

  • This variable is currently not supported in Oracle Reports distribution functionality as this is specific to PDF and printer outputs only.

See Also:

Oracle Application Server Reports Services Publishing Reports to the Web for more information on setting the JVM options.

9.3.4 Specifying the Values for Oracle Reports' Java Virtual Machine

You may want to set Oracle Reports’ Java Virtual Machine (JVM) options explicitly to get certain specific behaviors from the JVM that aren't enabled by default. To do this, use the command line option JVMOPTIONS.

You can use JVMOPTIONS to set options for Reports Runtime, Reports Builder, or Reports Converter's JVM. For example, you can use the following command line to start Reports Builder with a 512MB heap space:

rwbuilder jvmoptions=-Xmx512M

You can set more than one option by enclosing the value in quotes:

rwbuilder jvmoptions="-Xmx256M -Xms=128M"

The syntax of JVMOPTIONS is

JVMOPTIONS=option | "option [option]"

where option is a valid option for a Reports JVM.

The default value for JVMOPTIONS is -Xmx256M.


The value of JVMOPTIONS overrides the value in the REPORTS_JVM_OPTIONS environment variable.

9.3.5 Resolving Reports-Portal Integration Error When Attempting OID Create Resource

In OracleAS Portal, when you have configured Oracle Reports Security settings for Reports Definition File Access by editing a reports definition file, you may encounter the following error when you click Run or Run as Portlet:

500 Internal Server Error
Unexpected Error. Please contact Administrator

This error occurs when all of the following conditions are true:

  • You have an Interop deployment (which allows for a mixed 9.0.2/9.0.4 environment), with 9.0.4 MT (mid-tier), 9.0.4 IM (Identity Management), and 9.0.2 MR (metadata repository) configured to run together.

  • You are running Oracle Reports within OracleAS Portal, using the SSOCONN parameter.

  • The connection resource you specify in the SSOCONN parameter was not created in the Oracle Internet Directory (OID) server.

To work around this issue, do the following:

  1. In the 9.0.4 IM Oracle home, open the following file in a text editor:


  2. Add the following line to the file:

    OssoRedirectByForm on

    For example:

    <IfModule mod_osso.c>
    OssoIpCheck off
    OssoIdleTimeout off
    OssoRedirectByForm on

9.3.6 Running to Web Layout on Reports Builder

You can preview a report from Reports Builder by using the Run To Web Layout functionality. You do not need to have the Reports Server configured in order to use this functionality, because Reports Builder includes an embedded Oracle Application Server Containers for J2EE(OC4J) server.

After you upgrade to Oracle Reports 10g (9.0.4) from Oracle9i Reports Release 2 (9.0.2), you must ensure that the location in the environment variables CLASSPATH or REPORTS_CLASSPATH refer only to the oc4j.jar file in the 10g (9.0.4) Oracle home. You must remove the path to the 9.0.2 Oracle home oc4j.jar if it exists in either REPORTS_CLASSPATH or CLASSPATH.

If you include the 9.0.2. oc4j.jar file path in either CLASSPATH or REPORTS_CLASSPATH, the Run to Web Layout functionality will fail with the following error:

The major.minor version '48.0' is too recent for this tool to understand

9.4 Administration Issues and Workarounds

This section describes administration issues and their workarounds for Oracle Reports Developer.

9.4.1 Authenticating EM Access to Reports Server Information

The identifier element in server_name.conf contains a new value called SERVERACCESSKEY. This value is used to ensure that the Reports Server information in Oracle Enterprise Manager (EM) is secure. The following authentication is implemented:

  • The value of the identifier element in the server_name.conf file is encrypted and is of the form %SERVERACCESSKEY_USER%/%SERVERACCESSKEY_PASSWORD%. For example:

    <identifier confidential="yes" encrypted="no">
  • The corresponding entries in the targets.xml file are:


The default installation ensures that the install time values of %SERVERACCESSKEY_USER% and %SERVERACCESSKEY_PASSWORD% match those in targets.xml.


%SERVERACCESSKEY_USER% and %SERVERACCESSKEY_PASSWORD% in server_name.conf and targets.xml must match for the Reports Server pages in EM to display data correctly.

To change the user name and password:

  1. Edit the oracle_home/reports/conf/server_name.conf file, as follows:

    <identifier confidential="yes" encrypted="no">
  2. Edit the oracle_home/sysman/emd/targets.xml file, as follows:

    <Property NAME="UserName" VALUE="new_username" ENCRYPTED="FALSE"/>
    <Property NAME="Password" VALUE="new_password" ENCRYPTED="FALSE"/>
  3. Restart EM and Reports Server. The user name and password in server_name.conf and targets.xml will be encrypted after the restart.


Beginning with Oracle Reports 10g (9.0.4), Enterprise Manager (EM) will not use OID authentication to access Reports Server information. It will use the SERVERACCESSKEY value to specify the authentication.

9.4.2 Running Reports on OracleAS Portal as an Item Link

When you install OracleAS Portal with a non-default language setting, some entries required to publish a report as an item link on a portal page are not installed automatically. You must install the language of your choice by using the rwlang.sql script.

Run the script rwlang.sql in the directory oracle_home/portal/admin/plsql/wwd/ if:

  • You selected at least one language in addition to the default ("US") when you installed OracleAS Portal

  • You want to publish a report as an item link in OracleAS Portal.

This is a one time post-installation task and will ensure that you can publish a report as an item link on OracleAS Portal.

To run the script:

  1. Navigate to the directory oracle_home/portal/admin/plsql/wwd/.

  2. Run SQL*Plus.

  3. Logon to OracleAS Portal using the portal schema.


    This is the portal schema you used to install OracleAS Portal PL/ SQL packages.

  4. Run the script rwlang.sql with a list of language identifiers corresponding to the languages you installed with OracleAS Portal:

    @rwlang.sql language_list

    where language_list is a list of language identifiers, separated by commas.

    For example, if you installed French and Japanese when you installed OracleAS Portal, you would run the following command:

    @rwlang.sql f,ja.

Usage Notes:

  • Do not leave spaces before or after the comma (,), otherwise SQL*Plus will interpret the language list as two parameters, instead of one parameter containing a comma delimiter.

  • The file rwlang.sql contains a complete list of language identifiers. You can view the file with a text editor to find the identifiers you want.

9.5 Documentation Errata

This section describes known errors in the documentation.