|Oracle 9i Reports Release Notes (Patch 1)
Release 2 (9.0.2)
Part Number B10221-01
This chapter describes configuration issues and their work arounds for Oracle9i Reports.
During installation, if the Reports Configuration Assistant fails and gives the following message:
then perform the following procedures:
This creates the Reports portlet in Oracle9iAS Portal.
Alternatively, you can create a
tnsnames entry and execute the script as the Oracle9iAS Portal user with the user password obtained from the Oracle Internet Directory in Step 1.
After installation, if you are planning to use the Reports CGI, you should test it with the following URL:
This URL may fail with the following error:
If it does, you need to add the
bin directory and the Java Virtual Machine's .dll path to the Oracle HTTP Server's path. You can do this by adding the following entry to
<environment> <prop name="PATH"
On Linux, the in-process server does not start. To resolve this issue, you need to get the current value of the $HOME environment variable from your linux terminal session and then add the $HOME variable to the
reports.sh script in $ORACLE_HOME/bin:
The Reports Builder requires an instance of the Reports Server. Hence, when you install the Reports Builder, the Installer prompts you for some information that it requires to configure the Reports Server, for example the name of your mail server.
Bug number: 2224816
When you run JSP reports from Oracle9iAS Portal, you need to have a complete path for the CSS file because Oracle9i Reports and Oracle9iAS Portal have different virtual directories. For example, if you use
css/my.css for a JSP report in Oracle9iAS Portal, the browser will construct the URL as follows:
This URL will not work. The URL needs to be as follows, which requires you to enter a fully qualified path in the JSP report:
Oracle9i Reports uses the environment variable REPORTS_CLASSPATH when looking for Java classes; it does not use the system CLASSPATH variable. As a result, any JavaBeans that you want to use within Oracle9i Reports must be locatable from the REPORTS_CLASSPATH.
REPORTS_CLASSPATH is limited to 511 bytes in length. For Windows systems, REPORTS_CLASSPATH is set in the registry. For UNIX systems, it is set from the command prompt or in a shell script.
If you are planning to run reports on an X-terminal or graphical terminal, the DISPLAY variable must be set appropriately. For more information on configuring for X-terminals and graphical terminals, refer to the platform-specific documentation for Oracle9iAS.
REPORTS60_DEFAULT_PIXEL_SIZE is an environment variable that overrides the operating system's default pixel size when rendering a report. Normally, Oracle9i Reports takes its pixel size from the operating system. If you are working with older reports that rely upon a pixel size that is different from that of the operating system (for example, a pixel size of 80), you can use this variable to maintain the same behavior in your older reports.
For Windows, REPORTS60_DEFAULT_PIXEL_SIZE is set in the registry. For UNIX, it is set from the command prompt or in a shell script.
Oracle9i Reports allows you to run Oracle6i Graphics for backward compatibility purposes. Therefore, the Oracle6i Graphics charts in a Reports6i report should continue to run correctly when the report is opened and run in the Oracle9i Reports environment. To ensure that this functionality works, you must:
g90runm.shand ensure that your Oracle6i home/bin directory is in that path.