|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for hp-ux PA-RISC (64-bit) B15511-05 |
|
 Previous |
 Next |
|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for hp-ux PA-RISC (64-bit) B15511-05 |
|
|
Previous |
Next |
This chapter describes issues associated with Oracle Business Intelligence. It includes the following topics:
Section 16.3, "Oracle Business Intelligence Discoverer Plus Relational"
Section 16.4, "Oracle Business Intelligence Discoverer Plus OLAP"
Section 16.5, "Oracle Business Intelligence Discoverer Portlet Provider"
Section 16.6, "Oracle Business Intelligence Discoverer Viewer"
Section 16.7, "Oracle Business Intelligence Discoverer EUL Command Line for Java"
This section describes installation issues for Oracle Business Intelligence products. It contains the following topic:
Section 16.1.1, "Dialog Obscured During Non-Interactive Installation"
Section 16.1.2, "Association with Oracle Identity Management"
Even if you perform a non-interactive installation, the NetCA dialog will continue to be displayed during the configuration phase of installation. The NetCA dialog might be displayed behind the Oracle Universal Installer window or splash screen. Because the NetCA dialog is waiting for a response, you could get the mistaken impression that installation has halted prematurely. To continue with the installation, perform the following steps:
Move the Oracle Installer window to reveal the NetCA dialog.
Click Next.
Click Finish.
This section describes general issues and workarounds for Oracle Business Intelligence products. It contains the following topics:
Section 16.2.1, "Database Requirements for Oracle Application Server Discoverer"
Section 16.2.2, "Sun Java Plugin, Oracle JInitiator and the Plastic Look and Feel"
Section 16.2.3, "Resizing Issue with Mozilla and Firefox Browsers"
Section 16.2.8, "Query Prediction Requires the Majority of the Query Time"
This section clarifies the database requirements for OracleAS Discoverer 10.1.2 as it relates to an Oracle8i Database and as stated in the following installation guides:
Oracle Business Intelligence Installation Guide for Windows and Solaris (SPARC)
Oracle Business Intelligence Installation Guide for HP-UX PA-RISC (64-bit) and Linux x86
In general, Oracle Business Intelligence follows the customer database support and certifications in the associated Oracle Application Server release. Oracle Application Server 10.1.2 (including OracleAS Discoverer) is certified and supports connections to customer databases running Oracle9i Database (release 9.2) and Oracle Database 10g (10.1). Consult the Certify application on Oracle Metalink for details.
The database requirements that are specified in the installation guides for querying a multidimensional data source are complete and correct. The database requirements for querying a relational data source are also complete and correct but need further clarification.
OracleAS Discoverer 10.1.2 running against a relational data source has been certified (that is, tested and known to work) against Oracle9i Database (release 9.2) and Oracle Database 10g (10.1). OracleAS Discoverer 10.1.2 running against a relational data source is supported against either of these fully supported versions of the Oracle Database -- Oracle9i Database or Oracle Database 10g. An OracleAS Discoverer 10.1.2 connection to and running against the Oracle8i Database is not supported.
Desupport for the Oracle8i Database has been announced and all customers are encouraged to upgrade to Oracle9i Database or Oracle Database 10g. Consult the following notes on Oracle Metalink for additional information:
You can specify in Oracle Application Server Control, whether you want to use the Plastic look and feel in Oracle Business Intelligence Discoverer Plus (Relational and OLAP). If you want to use the Plastic look and feel, you must use the Sun Java Plugin 1.4.2. If you are using Oracle JInitiator 1.3.1.x, then you have to select a look and feel other than Plastic, such as the Browser look and feel.
When you use Oracle Business Intelligence Discoverer Plus Relational or Oracle Business Intelligence Discoverer Plus OLAP with Mozilla and Firefox browsers (version 1.5 and later) and you resize the browser window, the browser can freeze and might crash the applet intermittently. This issue is caused by the following bugs in the Sun Java Runtime Engine: 4836462 and 5076485.
To work around this issue, do not resize the applet window or use a different browser, such as Microsoft Windows Internet Explorer.
Under certain rare circumstances, PDF printing of worksheets might require additional memory when there are many columns, even if there is a small number of rows. To work around this issue, either rotate the column axis with the row axis and try to print again, or increase the memory for the OC4J_BI_Forms JVM process, as described in Oracle Application Server Discoverer Configuration Guide.
Under some circumstances in Oracle Business Intelligence Discoverer Plus and Oracle Business Intelligence Discoverer Viewer, a PDF generator might be unable to generate PDF because of the size. Some examples of such cases are described in the following list:
The graph is larger than the page size.
The sum of the row header column sizes is larger than the page size.
The sum of the row header column sizes plus any other column size is larger than the page size.
To work around this issue, adjust the graph size or row header size before trying to generate the PDF again.
You might notice unsightly font issues when using a non-English locale such as Czech. For example, when a worksheet uses a serif font, text in that worksheet might be displayed incorrectly on the screen and in printouts.
To work around this issue, update the file that maps the serif fonts. The name of this file differs depending on the locale in use. When you use Oracle Business Intelligence Discoverer Plus in English, the file is named file.properties. If you use Oracle Business Intelligence Discoverer Plus in a non-English locale, then the file name includes the code for the locale, such as file.properties.cs for Czech.
Update the mapping file with the following information:
serif.0=Times New Roman,EASTEUROPE_CHARSET serif.1=WingDings,SYMBOL_CHARSET,NEED_CONVERTED serif.2=Symbol,SYMBOL_CHARSET,NEED_CONVERTED
Consult the following Sun Web site for additional information about fonts:
http://java.sun.com/j2se/1.3/docs/guide/intl/addingfonts.html
Previous versions of Oracle Application Server Discoverer shipped with the files HWOnline.htm and Memo.doc, which were used to demonstrate 'drill out' functionality. To reduce disk space requirements and installation time, these files and instructions for their use will be made available from Oracle Technology Network:
http://www.oracle.com/technology/sample_code/products/discoverer/index.html
When using Oracle Application Server Discoverer with a relational data source, you can predict the time that is required to retrieve information by setting the value of the QPPEnable preference to 1. However, in some circumstances, the majority of the time taken to retrieve information will be consumed by the prediction activity itself.
To work around this issue, set the value of the QPPObtainCostMethod preference to 0 (use the EXPLAIN PLAN statement to predict query times), rather than to 1 (use dynamic views to predict query times).
For more information about setting preferences, refer to the Oracle Application Server Discoverer Configuration Guide.
The initial version of the Oracle Application Server Documentation CD (B14099-01) contains the following out-of-date documentation for Oracle Business Intelligence:
| Book Title | Part Number | Date |
|---|---|---|
| Oracle Business Intelligence Discoverer Configuration Guide | B13918-01 | September 2004 |
| Oracle Business Intelligence Discoverer Plus User's Guide | B13915-01 | September 2004 |
| Oracle Business Intelligence Discoverer Viewer User's Guide | B13987-01 | September 2004 |
| Oracle Business Intelligence Discoverer EUL Command Line for Java User's Guide | B13919-01 | September 2004 |
You can find updated versions of these books (and two additional books) in the /doc/docs.htm subdirectory on the Oracle Business Intelligence CD 1, as follows:
| Book Title | Part Number | Date |
|---|---|---|
| Oracle Business Intelligence Concepts Guide | B13970-01 | November 2004 |
| Oracle Business Intelligence Discoverer Configuration Guide | B13918-02 | November 2004 |
| Oracle Business Intelligence Discoverer Plus User's Guide | B13915-02 | November 2004 |
| Oracle Business Intelligence Discoverer Viewer User's Guide | B13987-02 | November 2004 |
| Oracle Business Intelligence Discoverer EUL Command Line for Java User's Guide | B13919-02 | November 2004 |
| Oracle Business Intelligence Discoverer Publishing Workbooks in Oracle Application Server Portal | B14465-01 | November 2004 |
The additional and updated books are also available on OTN at:
http://www.oracle.com/technology/documentation/appserver1012.html
or
This section provides information about corrections to published documentation. It contains the following topics:
Section 16.2.10.1, "Corrections to the Oracle Application Server Discoverer Configuration Guide"
Section 16.2.10.2, "Corrections to the Oracle Application Server Control Help"
There are errors in the Oracle Application Server Discoverer Configuration Guide in Chapter 5, "Managing and configuring OracleBI Discoverer." The errors exist in Section 5.6, "About configuring the options for the Discoverer Service and Discoverer client tier components." There are three references to 'servlet logging', relating to OracleBI Discoverer Plus, OracleBI Discoverer Viewer, and OracleBI Discoverer Portlet Provider, and each of these references should read 'session logging ' instead.
There is an error in the Oracle Application Server Control help for each of the OracleAS Discoverer component configuration pages (that is, Plus Configuration, Viewer Configuration, and Portlet Provider Configuration). The help uses the word 'servlet' when referring to setting the logging level, when it should instead use the word 'session'.
This section provides release notes for Oracle Business Intelligence Discoverer Plus Relational (OracleBI Discoverer Plus Relational). It contains the following topics:
Section 16.3.3, "Exporting Parameterized Data to Microsoft Excel Web Query Format"
Section 16.3.4, "Japanese Characters Not Visible After PDF Export"
The Color Palette Editor and all color chooser dialogs in OracleBI Discoverer Plus Relational have been modified so that users can add custom colors to the standard 49-color palette. Information about this enhancement is included in the documentation for this release, but you cannot access this information using context-sensitive help (the help button is disabled). From within OracleBI Discoverer Plus Relational, display the Help system using the Help menu and locate the appropriate topics using the index or search mechanisms.
When you run OracleBI Discoverer Plus Relational with Sun Java Plug-in 1.4.2_04, the Browser Look and Feel, and an Asian language (such as Japanese, Korean, or Chinese), you might notice that static text and text in buttons in the user interface appears truncated or clipped. To work around this issue, do one of the following:
Change the Look and Feel to either Plastic or System.
Use JInitiator 1.3.1.17 instead of the Sun Java Plug-in.
If you export a worksheet with a parameter that has an index available, the Export Wizard dialog: Parameter Prompts page contains an extra field.
The Parameters table contains an extra column called Type, which has a drop down list that contains two values:
Value -- Use 'Value' to prompt Excel end users to enter an item value at the Enter Parameter Value dialog in Microsoft Excel. For example, the LOV for a Month parameter might contain January, February, and March.
Index -- Use 'Index' to prompt Excel end users to enter an index value at the Enter Parameter Value dialog in Microsoft Excel. For example, the LOV for a Month parameter might contain 1 (for January), 2 (for February), and 3 (for March).
In some circumstances, Japanese characters are not displayed in the title or the text area of a worksheet that has been exported to PDF. This problem occurs when the text in the title or text area uses the Dialog font. To work around this problem, change the font of the text in the title or text area to other font (such as Monospaced) so that non-ASCII data can be exported to PDF correctly.
This section provides release notes for Oracle Business Intelligence Discoverer Plus OLAP (OracleBI Discoverer Plus OLAP). It contains the following topics:
Section 16.4.1, "Accepting the Default Setting for the OPTIMIZER_FEATURES_ENABLE Parameter"
Section 16.4.4, "SID Length Should be Less than 9 Characters"
Section 16.4.5, "Performance Issues or Errors when Suppressing NA or Zero Values"
Section 16.4.8, "Link Tool Works Incorrectly in Some Locales"
Section 16.4.9, "Link Tool Fails to Pass Parameters to OracleBI Discoverer Viewer"
Section 16.4.10, "Memory Issues when Exporting Extremely Large Graphs"
Section 16.4.13, "Printing Worksheets with Large Data Values"
If you recently upgraded the Oracle database, then you might have set the OPTIMIZER_FEATURES_ENABLE initialization parameter to a value that enabled you to maintain the optimizer behavior of a previous release.
OracleBI Discoverer Plus OLAP is a new product and takes advantage of the latest database features for optimal performance. OracleBI Discoverer Plus OLAP requires that the OPTIMIZER_FEATURES_ENABLE parameter be left at its default value for the respective database release (the default value is the database release number, such as 9.2.0.). Any other settings can lead to unexpected behavior.
Oracle does not recommend explicitly setting the OPTIMIZER_FEATURES_ENABLE parameter to an earlier release. Instead, resolve execution plan or query performance issues on a case-by-case basis.
There may be Oracle Business Intelligence Discoverer Plus applet download issues when caching has been enabled in the Sun Java Plugin. Disable caching in the plug-in to avoid this issue.
When you are running Netscape 7.x or Mozilla browsers, the Netscape and Mozilla Mail clients and Web browser may become disabled when OracleBI Discoverer Plus OLAP modal dialogs are displayed. Dismissing the OracleBI Discoverer Plus OLAP dialog resumes normal operation for the Netscape and Mozilla tools.
Due to a known bug, you cannot log in to OracleBI Discoverer Plus OLAP unless the SID contains 8 characters or less. To work around this issue, either change the existing SID to contain 8 characters or less or create a new database instance that has a SID of 8 characters or less.
In certain situations, you might encounter performance issues or errors when suppressing NA or zero data values in rows and columns in a worksheet. This issue has no workaround.
When you use the tab key to select items in a worksheet, the menus do not always synchronize to reflect the currently selected item. This issue has no workaround.
The ESC key does not close the following dialogs: Totals, New Total, Parameter, and Manage Catalog. Instead of using the ESC key, press the Close or OK button.
The Link tool, which enables users to drill out to external URLs from a crosstab cell, may not work correctly in all locales due to URL encoding issues. This issue has no workaround.
The Link tool, which enables users to drill to OracleBI Discoverer Plus OLAP Relational worksheets, will not pass parameters to OracleBI Discoverer Viewer. To work around this issue, perform the following steps:
Create a link for OracleBI Discoverer Viewer using the instructions in the "How to create links" topic in the OracleBI Discoverer Plus OLAP Help system.
Specify parameters for the link using the Parameters dialog.
Notice how the parameters are specified in the URL in the Destination box in the New Link dialog.
Modify the generated URL in the Destination box by replacing the characters "param" with the characters "qp", as shown in the following example:
param_param-name=value
should be changed to:
qp_param-name=value
Exporting extremely large graphs can cause memory issues, requiring a restart of the OracleBI Discoverer Plus OLAP session. This issue has no workaround.
Repeated exports of a graph to an image format may cause the export to fail. This issue has no workarounds.
Reinvoking the Page Setup dialog from the Print dialog may cause the Page Setup dialog to be blank. This issue has no workaround.
When printing a worksheet that contains large numbers in the data cells, the string ####### may be printed instead of the actual numbers. This issue has no workaround.
Non-empty titles and text areas will be printed even if they are hidden in the worksheet. This issue has no workaround.
When you use JAWS, you will notice errors when you attempt to format graphs and crosstabs using the Format dialogs. This issue has no workaround.
This section contains the following topics that relate to the Discoverer Catalog:
Section 16.4.16.2, "Enabled Partitioning Option for Discoverer Catalog Installation"
Section 16.4.16.3, "Incorrect Error Message Specified In Documentation"
Due to a known bug, some objects are created in the default tablespace of the Discoverer Catalog owner, D4OSYS. Due to this object creation, the default user tablespace for D4OSYS also needs to comply with the 8KB block size requirement that is outlined in Chapter 6 of the Oracle Application Server Discoverer Configuration Guide.
To work around this issue, before you install the Discoverer Catalog, create the Catalog owner and set the default tablespace to match the target tablespace for the Discoverer Catalog installation. The following line provides a sample command for this workaround:
create user d4osys identified by %pwd% default tablespace %8k_tablespace%"
Due to a known bug, you cannot install the Discoverer Catalog if the Partitioning option is not enabled in the database. Contact Oracle Support Services for information on resolving this issue.
Chapter 6 of the Oracle Application Server Discoverer Configuration Guide has a section with the title of "Checking the block size when installing the Discoverer Catalog". That section states that you might see an error message such as the following one if you try to install the Discoverer Catalog when the block size is not large enough:
ORA-01450: maximum key length number exceeded
This statement is incorrect. You will not see the ORA-01450 error message. Instead, you will see one similar to the following:
oracle.dss.d4o.administration.D4OInstallationException: D4O-1125 Post-install verification failed, not all Discoverer Catalog objects are installed. Expected xx, found yy where xx is the number of objects expected and yy is the number of objects found.
Even though the error message is stated incorrectly, the way that you resolve the block size issue is described correctly. If you want to see the SQL trace from the installation of the Discoverer Catalog, then consult Note:295619.1 "Tracing Discoverer Catalog Installation", which is available on Oracle Metalink.
This section provides release notes for Oracle Business Intelligence Discoverer Portlet Provider (OracleBI Discoverer Portlet Provider). It contains the following topics:
To use OracleBI Discoverer Portlet Provider, Oracle Business Intelligence must be associated with an Oracle Application Server Metadata Repository (MR) 10.1.2 after installation. The OracleAS Metadata Repository is part of the Oracle Application Server Infrastructure.
To use OracleBI Discoverer Portlet Provider 10.1.2 with OracleAS Portal 9.0.4, you must upgrade one of the following:
The OracleAS Discoverer part of the OracleAS Metadata Repository 9.0.4
You upgrade the OracleAS Discoverer part of the OracleAS Metadata Repository using the upgradeMR script.
The entire OracleAS Metadata Repository
You upgrade the entire OracleAS Metadata Repository using the MRUA shipped with Oracle Application Server. Before upgrading the entire OracleAS Metadata Repository, ensure that you want to upgrade OracleAS Portal to 10.1.2. For example, upgrading OracleAS Portal to 10.1.2. prohibits using OracleAS Reports Services within OracleAS Portal.
Note: Before you can upgrade the OracleAS Metadata Repository, you must ensure that the database that hosts the repository is upgraded to a version that is supported by Oracle Business Intelligence 10g (10.1.2). Specifically, the database that hosts the OracleAS Metadata Repository must be Oracle Database 10g (10.1.0.3.1) or Oracle9i Database Server Release 2 (9.2.0.6).
You must also associate the 10.1.2 Oracle Business Intelligence installation with the same 9.0.4 Oracle Identity Management and OracleAS Metadata Repository as that being used by the OracleAS Portal instance.
To use OracleBI Discoverer Portlet Provider 10.1.2 with OracleAS Portal 9.0.4, perform the following steps:
Associate Oracle Business Intelligence with the Oracle Application Server Infrastructure that is associated with the OracleAS Portal that you want to use.
For information, see Chapter 2 of the Oracle Application Server Discoverer Configuration Guide.
Upgrade the OracleAS Discoverer part of the OracleAS Metadata Repository only or the entire OracleAS Metadata Repository, as follows:
For information about upgrading the OracleAS Discoverer part of the OracleAS Metadata Repository only, see Section 16.5.1.1, "How to upgrade the OracleAS Discoverer part of the OracleAS Metadata Repository".
For more information about upgrading the entire OracleAS Metadata Repository using the MRUA, see Oracle Application Server 10g Upgrading to 10g (9.0.4).
Do one of the following to set up OracleBI Discoverer Portlet Provider:
If you have an existing OracleBI Discoverer Portlet Provider 9.0.4 registered with OracleAS Portal, change the registration of that OracleBI Discoverer Portlet Provider to use the URL of OracleBI Discoverer Portlet Provider 10.1.2.
You typically change the registration of the OracleBI Discoverer Portlet Provider when you have existing 9.0.4 OracleAS Discoverer Portlets in the OracleAS Metadata Repository that you upgraded to 10.1.2.
If you do not have an existing OracleBI Discoverer Portlet Provider 9.0.4 registered with OracleAS Portal, register the OracleBI Discoverer Portlet Provider 10.1.2 with OracleAS Portal.
You typically register a new OracleBI Discoverer Portlet Provider when you do not have existing 9.0.4 OracleAS Discoverer Portlets in the OracleAS Metadata Repository that you upgraded to 10.1.2.
For more information, see Chapter 11 of the Oracle Application Server Discoverer Configuration Guide.
You upgrade the OracleAS Discoverer part of the OracleAS Metadata Repository to work with OracleBI Discoverer Portlet Provider 10.1.2 using a script that is located in the following place in the Oracle Business Intelligence installation:
ORACLE_HOME/discoverer/util/upgradeMR.sh
To upgrade an OracleAS Metadata Repository 9.0.4 to work with OracleBI Discoverer Portlet Provider 10.1.2, complete the following steps:
Before running the script, ensure that the ORACLE_HOME environment variable is set to the OracleAS Discoverer home directory.
On the OracleAS Discoverer machine, open a command prompt and run the upgradeMR script.
You are prompted to confirm that you want to upgrade the OracleAS Discoverer schema in the OracleAS Metadata Repository to 10.1.2.
Enter 'Y' or 'y' in response to the prompt.
You are prompted to enter a user name and password.
When prompted, enter the user name and password of the SYSTEM user on the OracleAS Metadata Repository database.
Output from the script is displayed on the console and is also logged in the MRUpgrade.log file in the util directory. For example, on Solaris the log file is located in:
ORACLE_HOME/discoverer/util/MRUpgrade.log.
Important: Once you upgrade the OracleAS Discoverer part of the OracleAS Metadata Repository, you will only be able to use the OracleBI Discoverer Portlet Provider 10.1.2. You will no longer be able to use the OracleBI Discoverer Portlet Provider 9.0.4 with this OracleAS Portal and Infrastructure.
If you have a worksheet with parameters that use lists of values (LOVs), then you will get a "404 Not Found" error in the following situations:
When you click "Analyze" to launch OracleBI Discoverer Viewer.
When you click on the search icon for the LOV list.
To work around this issue after launching OracleBI Discoverer Viewer, run the worksheet again by pressing the Go button, then use the LOV dialog to change the parameter values.
You might encounter one or both of the following situations:
An error when you edit defaults for worksheets from OracleBI Discoverer Plus OLAP in the second step of the Edit Default wizard.
Every page in the Edit Default wizard loading twice.
These situations occur when the "Web provider in same cookie domain as the portal" box is selected when you register OracleBI Discoverer Portlet Provider.
To work around this issue, display the registration settings for OracleBI Discoverer Portlet Provider. Ensure that the "Web provider in same cookie domain as the portal" box is not selected.
This section provides release notes for Oracle Business Intelligence Discoverer Viewer (OracleBI Discoverer Viewer). It contains the following topic:
When the Web browser language is different from the connection locale, the Help system is not displayed in OracleBI Discoverer Viewer. To work around this issue, set the language of the Web browser to be the same as the connection locale language and the Help system for OracleBI Discoverer Viewer will display properly.
There are no known issues for the Oracle Business Intelligence Discoverer EUL Command Line for Java.
This section describes some known issues with the Oracle9i (Release 2) OLAP option that affect all products accessing OLAP data, including OracleBI Discoverer Plus OLAP.
You may encounter performance problems, particularly with large dimensions, if you suppress NA or zero values.
If you have a complex query that involves a moving total calculation, then when you navigate the query results, you may see an ArrayIndexOutOfBounds exception.
At times, database resources are not properly released. This may result in excessive memory consumption. To release the resources, close OracleBI Discoverer Plus OLAP or OracleBI Discoverer Viewer.
