| Oracle® Developer Suite Release Notes 10g Release 2 (10.1.2) for Solaris Operating System (SPARC), Microsoft Windows, and Linux x86 B16010-05 |
|
 Previous |
 Next |
| Oracle® Developer Suite Release Notes 10g Release 2 (10.1.2) for Solaris Operating System (SPARC), Microsoft Windows, and Linux x86 B16010-05 |
|
Previous |
Next |
This chapter describes issues associated with Oracle Business Intelligence Beans (OracleBI Beans). It includes the following topics:
If you installed OracleBI Beans as part of Oracle Developer Suite, then you must obtain and install the standalone version of OracleBI Beans from Oracle Technology Network. By installing the standalone version, you ensure that your installation contains an important fix for a Globally Unique ID (GUID) generation issue.
You might notice intermittent problems with OracleBI Beans projects that are created in JDeveloper. These problems are often caused by the fact that the project's J2EE root context contains blank spaces, which in turn is caused by the fact that the project's name contains spaces.
To work around these problems, simply avoid including spaces in the project name. If you really prefer to include spaces in a project name, then modify the default J2EE context root that JDeveloper generates for the project by accessing the Project Settings dialog.
You might encounter a problem with the executeCommand method of the Connection object if the input OLAP DML string or the output log information is too long. If this happens, then use the DBMS_AW PL/SQL package through JDBC.
If you have a Family step that is followed by a KEEP action on an asymmetric saved selection, then you might see duplicate results when connecting to an Oracle9i (Release 2) database, version 9.2.0.6. This issue has no workaround.
The following issues exist for presentations in OracleBI Beans:
Because of Sun Java J2SE 1.2 bug 4151279 and Sun J2SE 1.4 regression bug 4749538, pie graphs and other graphs with circular components may not render optimally. You can help to resolve this issue by setting the graph's graphicAntialiasing property to True.
When printing a crosstab that contains large numbers in the data cells, the string ####### may be printed instead of the actual numbers. This issue has no workaround.
In the Java-client crosstab toolbar, the Start Align button always aligns text to the left. For locales that read right-to-left, use the Right Align button.
The following issues exist for HTML-client applications in OracleBI Beans:
In HTML-client applications, an application developer can allow end users to enter custom text for tooltips in thin graphs. Developers must be aware that this practice enables users to enter JavaScript that could be used for malicious purposes. Developers are advised to prohibit end users from entering custom text for tooltips in a thin graph.
In HTML-client applications, popup windows (Lists of Values, or LOVs) may stop working in browsers that have third-party toolbars or popup blockers installed, such as the Google or Yahoo toolbars. The following OracleBI Beans components use LOVs:
In data views, paging controls launch a FindMember popup.
QueryBuilder and CalcBuilder launch an LOVContainer popup.
You can work around this issue by disabling or hiding the offending toolbars.
Occasionally when a partial page rendering action is used to update a component that is contained in paragraph elements (<p>) or invalid HTML, the component might not update correctly and a JavaScript error is generated. To work around this issue, do not place the component in paragraph elements (<p>) or in invalid HTML.
The targetFolderListIds attribute of the BI Beans FolderList JSP tag allows a developer to specify the identifier of another FolderList tag as a target whose contents will be updated when a folder is selected. The FolderList tag does not automatically detect when a developer incorrectly specifies targets and creates a circular reference. For example, suppose that the following three FolderList tags exist on a page:
<orabi:FolderList id="A" targetFolderListIds="B"/> <orabi:FolderList id="B" targetFolderListIds="C"/> <orabi:FolderList id="C" targetFolderListIds="A"/>
When the page is run, the following infinite loop results:
FolderList A updates FolderList B FolderList B updates FolderList C FolderList C updates FolderList A
The FolderList tag does not detect this circular reference before the page is run.
Because of Sun JRE 1.4 bug 4688797, you might encounter issues when connecting to a database schema while your computer has Turkish regional settings. You will encounter the issue when you attempt to connect to a database schema with a user name that contains certain letters, such as the letter 'I' or 'i', for example, in "bibdemo". See the Sun JRE bug for information on the letters that are affected.
To work around this issue, either do not use Turkish regional settings or use a user name that does not contain the affected letters.
The following accessibility limitations exist for OracleBI Beans:
The current version of the JAWS screen reader does not correctly identify and read tables in Java applications. This problem occurs in the JDeveloper Help system, which incorporates the OracleBI Beans Help system.
JAWS does not read the description for some of the panels in the OLAP Connection wizard.
The following Help topics related to calculations are incorrect:
In the "Variance Calculation" topic, the formula for the calculation is incorrect. The correct formula is "Base-Target".
In the "Percent Variance calculation" topic, the formula for the calculation is incorrect. The correct formula is "(Base-Target)/Target".
In the "Percent Markup calculation" topic, the formula for the calculation is incorrect. The correct formula is "(From - Markup)/Markup".
This section describes some of the known issues with the Oracle OLAP option. These issues affect all products that access OLAP data, including OracleBI Beans.
At times, database resources are not properly released in the Oracle9i (Release 2) OLAP option. This may result in excessive memory consumption. To release the resources, close OracleBI Beans.
Potential performance issues occur when running against analytic workspaces in Oracle OLAP 10g Release 1 version 10.1.0.4. To work around these issues, always check OracleMetalink for the appropriate Oracle OLAP patches at the following location:
Do not overwrite the OLAP client that ships with OracleBI Beans 10.1.2.1. OracleBI Beans ships with an OLAP client (that is, the olap_api.jar file) that communicates with all database versions (including Oracle Database 10g Enterprise Edition Release 2 version 10.2.0.1) that are supported by this release of OracleBI Beans.
Because of a known bug, do not overwrite the olap_api.jar file in the OracleBI Beans 10.1.2.1 installation directory with the olap_api.jar file from the installation directory for Oracle Database 10g Enterprise Edition Release 2.
