Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for Microsoft Windows (64-Bit) on Intel Itanium B25335-02 |
|
Previous |
Next |
This chapter describes issues with Oracle Reports. It includes the following topics:
Note:
|
This section describes general issues and their workarounds for Oracle Reports. It includes the following topics:
Section 14.1.1, "OracleAS Reports Services Demos Will Not Work If JServ is Configured"
Section 14.1.2, "Error While Editing Batch Registered Report in OracleAS Portal"
Section 14.1.3, "Limitation on Linked Queries for DelimitedData Output"
Section 14.1.6, "PL/SQL Compilation Failure When Using SQL Constructs"
To run OracleAS Reports Services demos properly, do not configure Apache JServ on the computer where OracleAS Reports Services is installed.
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.
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.
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="https://xyz.mycompany.com:443/reports/rwservlet"/> ...... </Target>
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.
PL/SQL compilation may fail if you use SQL constructs in your reports and if the following conditions are present:
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 10.1.0.4 or later.
Move those SQL constructs to the server-side stored procedures.
Use the SQL constructs within SQL queries directly instead of procedures.
This section describes vendor-specific issues and their workarounds for Oracle Reports. It includes the following topics:
Section 14.2.1, "Underlines Do Not Display in HTMLCSS Output in Browser"
Section 14.2.2, "JSP-Based Web Report with Large Number of Columns Generates JSP Compilation Error"
Section 14.2.3, "Java AWT Windows Hangs with Specific Graphics Cards"
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.
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: Errors ... 6764 code too large for try statement catch( Throwable e) {18 code too large public void _jspService(HttpServletRequest request, HttpServletResponse response) throws java.io.IOException, ServletException}
This occurs due to a limitation in the Java language that does not enable compilation of Java files with large methods.
When you start Reports Server with rwserver.exe
, the UI may not display and Reports Server may hang on computers with specific graphics cards (for example, ATI Rage XL PCI card). This occurs due to a problem with the UI mechanism used in Java.
As a workaround, start Reports Server with the JVMOPTIONS
command line keyword set as shown in the following example:
rwserver SERVER=test JVMOPTIONS="-Dsun.java2d.noddraw=true"
Note: It is recommended that you start Reports Server from OPMN. |
This section describes Globalization Support issues and their workarounds for Oracle Reports. It includes the following topics:
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.
Note: The middle tier's default encoding can be different from the Servlet's encoding. For example, when you setLANG 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.
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 |
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.