3 Configuration Issues and Workarounds

This chapter describes configuration issues and their work arounds pertaining to previous patch releases, that is, Patch Release 1 and Patch Release 2 of Oracle9iAS Reports Services.

3.1 Reports Configuration Assistant Fails during Installation

During installation, if the Oracle9i Reports Configuration Assistant fails and gives the following message:

Process destroyed exception (in the installer configuration palette)

then perform the following procedures:

Remove Security Page:

1. Log on to Oracle9iAS Portal.

2. Click Builder.

3. Click Navigator.

4. Click Contents for the Portal Design-Time Pages page group.

5. Click Pages.

6. Click Delete for the Oracle Reports Security page.

Remove Security Provider:

1. Log on to Oracle9iAS Portal.

2. Click Builder.

3. Go to the Build tab by clicking Build.

4. In the Providers portlet, type ORACLE REPORTS SECURITY in the name field.

5. Click Delete.

Run rwaddpag.sql:

1. Log on to the Oracle Internet Directory and obtain the Oracle9iAS Portal user database password.

2. Log on to the metadata repository as the Oracle9iAS Portal user and run the following script:

   ORACLE_HOME/portal/admin/plsql/wwd/rwaddpag.sql
   
   

   This creates the Oracle9i 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.

3.2 Reports CGI Not Starting on Windows

After installation, if you are planning to use the Oracle9i Reports CGI, you should test it with the following URL:

http://server_name.domain:port_number/cgi-bin/rwcgi.exe/help?

This URL may fail with the following error:

Premature end of script headers: $ORACLE_HOME/bin/rwcgi.exe

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 $ORACLE_HOME\opmn\conf\opmn.xml:

<environment>
  <prop name="PATH" 
     value="%ORACLE_HOME%\bin;%ORACLE_HOME%\jdk\jre\bin\classic"/>
</environment>

3.3 In-process Server Not Starting on Linux

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:

HOME=env_value_of_HOME; export HOME

3.4 Reports Server Installed with Reports Builder

Reports Builder requires an instance of the Reports Server. Hence, when you install 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.

3.5 Running JSP Reports from Oracle9iAS Portal

Bug number: 2224816

When you run JSP reports from Oracle9iAS Portal, you need to have a complete path for the CSS file because Oracle9iAS Reports Services 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:

http://server:port/portal-path/css/foo.css

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:

http://server:port/reports/css/foo.css.

3.6 REPORTS_CLASSPATH

Oracle9iAS Reports Services 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 Oracle9iAS Reports Services 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.

3.7 X-terminals and Graphical Terminals

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 Oracle9i Application Server.

3.8 REPORTS60_DEFAULT_PIXEL_SIZE

REPORTS60_DEFAULT_PIXEL_SIZE is an environment variable that overrides the operating system’s default pixel size when rendering a report. Normally, Oracle9iAS Reports Services 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.

3.9 Oracle Reports 6i Access to Oracle9iAS Reports Services

Oracle9iAS Reports Services enables 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 Oracle9iAS Reports Services environment. To ensure that this functionality works, you must:

On All Platforms:

Make sure the tnsname entry used by Oracle9i Reports exists in both the Oracle9i and Oracle6i tnsnames.ora file in ORACLE_HOME/network/admin.

On Solaris and other Unix platforms:

If you encounter the following error:

SSL fatal error: cannot execute g90runm

You must do the following:

1. Specify the path of your ORACLE6i_HOME in the ORACLE_GRAPHICS6I_HOME variable in g90runm.sh and ensure that your ORACLE6i_HOME/bin directory is in that path.

2. In $ORACLE_HOME/bin/g90runm.sh, create a link to g90runm as:

   ln -s g90runm.sh g90runm
   

On Windows

1. Ensure that, in your registry, ORACLE_GRAPHICS6I_HOME points to the ORACLE6i_HOME\bin directory.

2. Add ORACLE6i_HOME\bin to the PATH environment variable.