| Oracle® Business Intelligence Suite Enterprise Edition Release Notes Version 10.1.3.2 Part No. B31773-07 |
|
| Oracle® Business Intelligence Suite Enterprise Edition Release Notes Version 10.1.3.2 Part No. B31773-07 |
|
Release Notes
Version 10.1.3.2
Part No. B31773-07
November 30, 2007
Oracle Business Intelligence Suite Enterprise Edition consists of components that were formerly available from Siebel Systems as Siebel Business Analytics Platform, with a number of significant enhancements.
These release notes describe known issues and workarounds for versions 10.1.3.2 and 10.1.3.2.1.
These release notes describe known issues and workarounds for the products that are on the Oracle Business Intelligence Suite Enterprise Edition CD. To install these products, consult the Oracle Business Intelligence Infrastructure Installation and Configuration Guide, which is available on the Oracle Business Intelligence Suite Enterprise Edition CD_ROM and from the Oracle Business Intelligence Suite Enterprise Edition Documentation Web site:
http://www.oracle.com/technology/documentation/bi_ee.html
The following list describes the sections of this document:
Section 4, "Oracle Business Intelligence Presentation Services"
Section 6, "Oracle Business Intelligence Interactive Dashboards"
Section 8, "Oracle Business Intelligence Disconnected Analytics"
Section 11, "Oracle Business Intelligence Administration Tool"
These release notes are updated periodically as new information becomes available. To ensure that you are reading the latest version of the release notes, check the Oracle Business Intelligence Suite Enterprise Edition Web site.
To find the Release Notes document
Click the following link:
In the section for the latest release, click View Library.
On the Documentation Library page, click the Getting Started tab.
On the Getting Started tab, in the Release Notes section, click PDF or HTML.
This section describes general issues and workarounds for Oracle Business Intelligence Suite Enterprise Edition products. It contains the following topics:
For certification information, refer to the System Requirements and Supported Platforms for Oracle Business Intelligence Suite Enterprise Edition document. This document is part of the Oracle Business Intelligence Suite Enterprise Edition documentation set. It is also available from the Certify tab on Oracle Metalink at the following location:
This section provides release notes on installing and upgrading Oracle Business Intelligence Suite Enterprise Edition. It contains the following topics:
Section 2.2.1, "Advanced Installation Requirements for Oracle Application Server"
Section 2.2.2, "Siebel Marketing Server Users Should Not Upgrade to Version 10.1.3.2"
Section 2.2.3, "Warning Messages Appear Despite Successful Upgrade"
Section 2.2.4, "Installation Hangs When _JAVA_OPTIONS Variable Set"
Section 2.2.5, "Microsoft .NET Installation Dialog is Displayed"
Section 2.2.6, "Cosmetic Issues to Ignore During Installation"
Section 2.2.7, "Host Name Errors After Installation on UNIX Platforms"
Section 2.2.8, "Issue Starting Javahost Service on Solaris Platforms"
Section 2.2.10, "Oracle BI Presentation Services Plug-In Deployed with all Custom Installations"
Section 2.2.11, "Oracle BI Presentation Services Does Not Start After Windows Installation"
Section 2.2.13, "Issue Starting Oracle BI Scheduler After Installing paint Repository"
Section 2.2.14, "Systems Management and Oracle BI Publisher Do Not Start After Installation"
Section 2.2.15, "Issue Logging into XMLP Server After Installation on SuSe Platform"
This issue applies to version 10.1.3.2. This issue is documented in version 10.1.3.2.1 of the Oracle Business Intelligence Infrastructure Installation and Configuration Guide.
If you plan to perform an Advanced Installation, be aware that Oracle Application Server must be installed in order for Oracle Business Intelligence installer to successfully deploy the applications. The following Oracle Application Server components are required:
Oracle HTTP Server
Oracle Containers for J2EE (OC4J)
Oracle Process Manager and Notification Server
If you do not want to use Oracle HTTP Server after installing Oracle Business Intelligence Suite Enterprise Edition, then you can disable Oracle HTTP Server in Oracle Application Server after the installation.
This issue applies to version 10.1.3.2. This issue is fixed in version 10.1.3.2.1.
If you are a customer of Oracle's Siebel Marketing Campaign Management product and you use the Siebel Marketing Server for segmentation, then you should not upgrade to Oracle Business Intelligence Suite Enterprise Edition version 10.1.3.2. Instead, you should upgrade only to version 10.1.3.2.1 or higher.
If you use Oracle's Siebel versions 7.7 and 7.8, then note that you must apply the patch on the respective versions, on the Siebel platform, for SOAP interoperability with Oracle Business Intelligence Suite Enterprise Edition version 10.1.3.2.1.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
During the upgrade process, you see various messages. You might see warning messages that mention a successful upgrade. Be aware that the use of "Warning" as a message category does not necessarily imply an unsuccessful upgrade operation. This issue has no workaround.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
If you run the Oracle Business Intelligence installer and notice that it hangs, for example at 4% complete, then check whether the _JAVA_OPTIONS environment variable is set. In the following example, the _JAVA_OPTIONS environment variable is set:
_JAVA_OPTIONS -Xrunjvmhook -Xbootclasspath/a:C:\PROGRA~1\COMMON~1\MERCUR~1\FUNCTI~1\Java\classes;C:\PROGRA~1\COMMON~1\MERCUR~1\FUNCTI~1\Java\classes\jasmine.jar
To work around this issue, comment out the line that sets the _JAVA_OPTIONS variable and the installation should proceed normally. Use syntax such as the following to comment out the line:
%_JAVA_OPTIONS %
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
When you run the Oracle Business Intelligence installer on Windows systems, you might notice that the Microsoft .NET installation dialog is displayed. If you see this dialog, then click either the Cancel or OK buttons there. In either case, the installation of Oracle Business Intelligence Suite Enterprise Edition proceeds normally.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
You can ignore the following cosmetic issues during installation:
When you run the Oracle Business Intelligence installer on Windows or Linux systems, you might notice text such as "$Lcom.siebel.analytics" appearing where the descriptions should be at the start of a full installation. This text can be displayed for approximately 30 seconds before a more meaningful description appears.
While this text might be construed as an error with installation, it is simply a refreshing issue that you can ignore once it disappears. Then you can continue with the installation.
On the "Installing Oracle Business Intelligence 10.1.3.2.0" progress page, the progress bar quickly shows 100%, even though the progress window indicates that files are being installed. In addition, the text for 100% is in reverse video (a pale grey), which is not very readable.
This issue has no workaround and does not hinder a successful installation.
This issue applies to version 10.1.3.2.1.
After installation on a UNIX platform, you might encounter errors such as the following ones:
When you click the BI Publisher tab on the Oracle BI Answers page, the page appears to "hang," giving no response.
When you click the BI Publisher tab on the Oracle BI Dashboard page, you see an error message similar to the following one:
The following error occurred: [code=DNS_HOST_NOT_FOUND] The host name was not found during the DNS lookup.
These errors occur because the installer cannot locate a valid full host name. The installer tries to obtain the full host name by using the "nslookup" command. If the "nslookup" utility is installed and working correctly, then the installer can find and use the full host name. If the "nslookup" utility is not installed or is not working correctly, then the installer cannot find the full host name. Instead, the installer tries to use the original machine name without the domain name.
To work around this issue, ensure that the "nslookup" utility is installed and working correctly on the UNIX machine so that the installer can find the full host name to use in configuration files. Otherwise, the installer will use only the original machine name, which can produce errors.
This issue applies to version 10.1.3.2.1.
After installing Oracle Business Intelligence Suite Enterprise Edition on Solaris platforms, you might see an error message such as the following one:
Javahost service is unable to start, exiting with the following error: "...SEVERE: Unexpected Exception. Listener will be shutdown. java.io.IOException: Invalid argument..."
This error is likely caused by Solaris bug (6433853). To resolve this issue:
Upgrade to the latest Java version for Solaris., which is 1.5.0_08 or later.
Ensure that the Javahost service uses the new Java version by completing these steps:
Open the instanceconfig.xml file in the SADATADIR/web/config directory for editing.
Modify the JavaHome element to point to the 1.5.0_08 or later version.
See the Oracle Business Intelligence Presentation Services Administration Guide for information on editing the instanceconfig.xml file.
This issue applies to version 10.1.3.2. This issue is fixed in version 10.1.3.2.1.
Before leveraging the multiuser development capabilities in Oracle Business Intelligence Enterprise Edition, ensure that you install a QuickFix for Oracle Business Intelligence Enterprise Edition 10g Release 3 version 10.1.3.2. You can access the QuickFix by locating Alert 1280 on SupportWeb at the following location:
The QuickFix resolves a bug that can cause projects that are checked out to be missing dimensional columns. This problem is the result of an Oracle BI Enterprise Edition defect in the way that the project extraction occurs under the following conditions:
The Logical Column on which it is based is not a Fact Column.
By default, read permission is not allowed. Everyone is set explicitly to have no visibility.
The project extraction sequence decides which presentation columns to add based on the project users. However, project users and groups are not added until after the fact tables of the project are added. Therefore, when fact tables (and the subsequent logical columns) are added, no presentation columns are added yet. Presentation columns are added in the next phase of the project extraction sequence when users and groups are added. The project extraction sequence for adding users and groups, however, only handles adding presentation columns based on fact columns. Columns based on dimension columns are not added unless their default permissions allow read access.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
If you perform a custom installation on a machine on which an HTTP server has been installed and if you choose to install Oracle Business Intelligence Presentation Services, then the Oracle BI Presentation Services Plug-in is deployed even if you do not select it. To avoid the plug-in being used, manually stop it after installation or undeploy it using Oracle Enterprise Manager.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
After installing on a Windows system and after rebooting the computer, you might find that Oracle BI Presentation Services does not start. This can occur due to many other large processes or services starting at the same time, which causes Oracle BI Presentation Services to time out.
To work around this issue, restart Oracle BI Presentation Services manually after the computer has rebooted.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
After performing an Advanced installation on a Windows system and after rebooting the computer, you may encounter an error message that states that a service failed to start. The event viewer shows log information similar to the following:
Invalid repository file: Drive:\OracleBI\server\Repository\paint.rpd.
This message is generated because the Paint demo is available only for the Basic installation and not for the Advanced installation. You can ignore this error message. This issue has no work around.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
After installing the paint repository, you will notice that Oracle BI Scheduler is not pre-configured. If you try to start Oracle BI Scheduler without configuring it first, then you might see an error message such as the following:
Error 1064: An exception occurred in the service when handling the control request
To avoid encountering this error message after installation, configure Oracle BI Scheduler as described in the Oracle Business Intelligence Infrastructure Installation and Configuration Guide.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
After installation, you might try to start Systems Management or Oracle BI Publisher using their Internet shortcuts or the following links:
http://host.domain.com:port/xmlpserverhttp://host.domain.com:port/emIf OC4J does not start after you have installed Oracle Business Intelligence Suite Enterprise Edition and restarted the computer, then these components will not start either. To work around this issue, manually start OC4J before starting these components.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
After completing a successful installation on the SuSe platform, you can attempt to log into the XMLP Server from the following URL:
http://host.domain:port/xmlpserver
After entering the user name and password, you might see an error message with text such as: "500 server not found."
To resolve this issue, restart OC4J.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
For this release, the Oracle BI Microsoft Excel add-in is able to be translated. However, it has not been localized for this release due to its limited life expectancy. A localized resource file could be created to provide language support. The value of such a file would be short-lived, because this add-in's functionality is intended to be replaced by a more robust Oracle BI Plug-In for Microsoft Office.
This issue applies to version 10.1.3.2.1.
When you use a Firefox browser on the Solaris platform, you might encounter a known issue with popup descriptions. When you hover the mouse pointer over an item to pop up its description, you might notice that the description is truncated to a single line, even if it should display multiple lines. This issue does not occur on browsers such as Internet Explorer on Windows platforms. Windows browsers display the entire description.
This issue has no workaround.
This section provides information on documentation corrections for Oracle Business Intelligence Suite Enterprise Edition. It contains the following topics:
Section 2.5.3, "Corrections for Oracle Business Intelligence Server Administration Guide"
Section 2.5.4, "Corrections for Oracle Business Intelligence Enterprise Edition Deployment Guide"
This section describes the following corrections to the Oracle Business Intelligence Infrastructure Installation and Configuration Guide:
This issue applies to version 10.1.3.2. This issue is documented in version 10.1.3.2.1 of the Oracle Business Intelligence Infrastructure Installation and Configuration Guide.
Chapter 4, "Preparing to Install Oracle Business Intelligence" contains the "Process of Planning the Installation" section. The following text should be added to the end of that section:
To install Oracle Business Intelligence Suite Enterprise Edition and Oracle client software on the same machine, you must install the Oracle client software first. If you install the Oracle client software after installing Oracle Business Intelligence Suite Enterprise Edition, then you might change the Java SDK version for Oracle Business Intelligence Suite Enterprise Edition, which might result in runtime errors.
This issue applies to version 10.1.3.2.1.
Chapter 4, "Preparing to Install Oracle Business Intelligence" contains the "Oracle BI Server Environment Variables for IBM AIX" section. In two subsections, there are incorrect values for LDR_CNTRL = IGNOREUNLOAD@LOADPUBLIC@PREREAD_SHLIB@MAXDATA. These subsections and the correct values for each are as follows:
Subsection: "Deploying 32-bit Oracle BI Under IBM AIX"
export LDR_CNTRL = IGNOREUNLOAD@LOADPUBLIC@PREREAD_SHLIB@MAXDATA=0X80000000
Subsection: "Deploying 64-bit Oracle BI Under IBM AIX"
export LDR_CNTRL=IGNOREUNLOAD@LOADPUBLIC@PREREAD_SHLIB@MAXDATA=0x6000000000000000
In the subsection "Deploying 32-bit Oracle BI Under IBM AIX," the following sentence is incorrect:
Run the following commands to set your 32-bit Oracle BI deployment under AIX:
This sentence should read as follows:
The following 32-bit environment variables for AIX are set automatically by .variant.sh:
This issue applies to version 10.1.3.2.1.
In chapter 9, Configuring Oracle BI Presentation Services, in the section "Creating a WAR File for Oracle BI Presentation Services," the table shown before the procedure is incorrect. Replace that table with the following text:
This procedure uses the WAR file, located in the following directories:
Windows: OracleBI_HOME\web
UNIX: /usr/local/OracleBI/web
In the procedure in this same section, replace the procedure as follows:
To create or recreate a WAR file
Navigate to the Oracle Business Intelligence installation directory shown in the preceding list.
To create the WAR file, run the following jar command:
jar -cf Analytics.war -C app.
|
Note: You must include the period at the end of the command. |
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
In the Oracle Business Intelligence Presentation Services Administration Guide, the procedure for creating a custom message template for the proxy functionality is missing a statement in the SQL to connect to the correct db/connection pool to extract the target users, and so on.
To work around this issue, replace the code in Step 4 in the procedure for creating a custom message template in the "Creating a Custom Message Template for Proxy Functionality" section in the Oracle Business Intelligence Presentation Services Administration Guide with this code:
<XML>
<logonParam name="RUNAS">
<getValues>EXECUTE PHYSICAL CONNECTION POOL physical_dbname.conn_pool_name
select targetId from Proxies where proxyId='@{USERID}'</getValues>
<verifyValue>EXECUTE PHYSICAL CONNECTION POOL physical_dbname.conn_pool_name
select targetId from Proxies where proxyId='@{USERID}' and
targetId='@{VALUE}'</verifyValue>
<getDelegateUsers>EXECUTE PHYSICAL CONNECTION POOL physical_dbname.conn_pool_name select proxyId, proxyLevel from Proxies where
targetId='@{USERID}'</getDelegateUsers>
</logonParam>
</XML>
Also include this sample custom message template at the end of the procedure:
Sample Custom Message Template
<?xml version="1.0" encoding="utf-8" ?>
<WebMessageTables xmlns:sawm="com.siebel.analytics.web.messageSystem">
<WebMessageTable system="SecurityTemplates" table="Messages">
<WebMessage name="LogonParamSQLTemplate">
<XML>
<logonParam name="RUNAS">
<!-- for EXECUTE PHYSICAL CONNECTION POOL, SQL_Paint.SQL_Paint = -->
<!-- SAS Repository physical_dbname.conn_pool_name -->
<getValues>EXECUTE PHYSICAL CONNECTION POOL SQL_Paint.SQL_Paint
select targetId from Proxies where proxyId='@{USERID}'\</getValues>
<verifyValue> EXECUTE PHYSICAL CONNECTION POOL SQL_Paint.SQL_Paint
select targetId from Proxies where proxyId='@{USERID}' and targetId='@{VALUE}'\</verifyValue>
<getDelegateUsers>EXECUTE PHYSICAL CONNECTION POOL SQL_Paint.SQL_Paint
select proxyId, proxylevel from Proxies where targetId='@{USERID}'
</getDelegateUsers>
</logonParam>
</XML>
</WebMessage>
</WebMessageTable>
</WebMessageTables>
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
In the Oracle Business Intelligence Server Administration Guide, in the Completing Setup and Managing Oracle BI Repository Files chapter, in the Setting Up the Repository to Work with Delivers section, the steps to set up the SA System subject area are incomplete. The SA System subject area must be correctly set up in the Presentation layer of the Oracle Business Intelligence repository for Oracle Business Intelligence Delivers to function.
For the complete steps to set up the SA System subject area, refer to the Analytics Server Administration Guide Version 7.8.2, Revision A. Navigate to Chapter 7 Completing Setup and Managing Oracle BI Repository Files and the Setting Up the Repository to Work with Delivers section. The following information contained in this section is applicable to the Oracle Business Intelligence 10.1.3.2 release.
The Presentation layer metadata needs to contain the SA System folder, User table, and columns as shown in Figure 15.
Table 26 in the guide describes the columns for the User table of the SA System subject area folder.
The Analytics Server Administration Guide Version 7.8.2 Revision A is available on the Oracle Business Intelligence Enterprise Edition Documentation page on Oracle Technology Network at the following location:
http://www.oracle.com/technology/documentation/bi_ee.html
and on SupportWeb on the Documentation Updates page at the following location:
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
In the Oracle Business Intelligence Enterprise Edition Deployment Guide the example given in step 3 of the procedure on page 142 to change the default Presentation Services listener port is incorrect.References to the <RPC> node need to be removed. Step 3 should read as follows:
3. Within the <WebConfig> tags, assign the RPC Listener Port value for the BI Presentation Services instance, as shown in the following example.
<WebConfig>
<ServerInstance>
...
<Listener port="9715" />
...
</ServerInstance>
</WebConfig>
NOTE: In the preceding example, the RPC Listener port for the BI Presentation Services instance has been changed to port 9715 from the default of 9710.
This section provides release notes for Oracle Business Intelligence Server (Oracle BI Server). It contains the following topics:
Section 3.2, "Issues with Full Outer Join and WITH Clause on Oracle Database 10g"
Section 3.4, "Column Dropped When Using a Report as a Filter for Another Report"
Section 3.5, "INTERVAL Data Type is Imported as LONGVARBINARY"
Section 3.7, "Internal Assertion Error Message Displayed During Consistency Check"
Section 3.9, "Error Message About Oracle BI Server Not Running"
Section 3.10, "Misleading Error Message for Timed-Out SAP/BW Connection"
Section 3.11, "Initialization Block Fails to Execute When Attempting to Change User System Variable"
Section 3.12, "Potential Oracle BI Server Crash When Editing Repository in Online Mode"
Section 3.13, "TIMESTAMPDIFF Function Causes Incorrect Values for IBM DB2 on OS/390 and AS/400"
Section 3.14, "Documentation Correction for Enabling Query Cache"
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
On Windows systems, you can use a "drag and drop" feature in the Administration Tool for XMLA data sources (SAP/BW and Microsoft Analysis Server).
This capability allows for physical metadata objects (such as cubes) to be dragged and dropped into the Administration Tool as fully configured Business Model metadata, thus retaining metrics, attributes, and dimensions. This mitigates the need to manually redefine logical dimensional models from data sources that already contain rich dimensional metadata constructs.
Enable this feature by performing the following steps:
Install Oracle Business Intelligence Suite Enterprise Edition on a Windows system.
Create the Windows system variable called OBIAT_XMLA_DD with a value of Yes.
Restart the Administration Tool.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
If you use a version of Oracle Database 10g Release 2 prior to 10.2.0.3, you might encounter an issue with a Full Outer Join that causes severe database performance issues and appears to hang the database when the Oracle BI Server sends to the database SQL queries that include WITH clauses.
To work around this issue when using Oracle Database 10g Release 1 or 2, upgrade to Oracle Database 10g Release 2 Patch Set 2 (for 10.2.0.3). For performance reasons, this is the preferred workaround.
To work around this issue without installing Patch Set 2, modify the Database Features table using the Administration Tool. This configuration prevents the Oracle BI Server from sending SQL constructs that expose the issue in an unpatched Oracle Database 10g.
To modify the Database Features table:
In the Administration Tool, open the properties of the Physical Database metadata object.
Navigate to the Features tab.
Ensure the values for the PERF_PREFER_MINIMAL_WITH_USAGE and PERF_PREFER_INTERNAL_STITCH_JOIN entries are selected, that is, set to True.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
When you use certain combinations of Ago() columns with level-based measure columns, you might see an Oracle Database error such as "ORA-00942: table or view does not exist at OCI call OCIStmtExecute."
To work around this issue when using Oracle Database 10g Release 2, install Patch Set 2 (for 10.2.0.3) and turn on the native Full Outer Join support. For performance reasons, this is the preferred workaround.
To work around this issue without installing Patch Set 2, set "PERF_PREFER_INTERNAL_STITCH_JOIN" to True in the Database Features table, as described in Section 3.2, "Issues with Full Outer Join and WITH Clause on Oracle Database 10g".
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
When you use a report to constrain the results of another report and the child report has a filter on a measure, then the optimizer might eliminate the measure column from the final results. To work around this issue, add a superfluous measure filter to the parent report, such as the following one:
'measure'<>0
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
When you import a database object that contains columns of data with the INTERVAL type, you will find that the imported data has the LONGVARBINARY type. Oracle Business Intelligence Suite Enterprise Edition does not support the INTERVAL data type directly. The data should be imported with a data type of UNKNOWN.
To work around this issue, remove the data of type INTERVAL from the business mapping and do not include that data as part of a query request.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
You can disable the high-level options (that is Warnings, Errors, or Best Practices) on the Options tab in the Consistency Check window, but that disabling does not automatically uncheck the corresponding check boxes within the Messages tab. Because the system applies the settings in the Consistency Check window rather than on the Messages tab, the appropriate high-level options are disabled.
This issue has no workaround.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
If the repository contains an aggregate measure as a level key, then the Administration Tool displays an Internal Assertion Error message. The message is displayed because an aggregate measure should not be defined as a level key.
To work around this issue, remove the aggregate measure from the level key and replace it with the correct key.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
When you are importing from an XMLA data source, you might see one of the following error messages, which might be inappropriate or misleading:
[nQSError : 46100] Sax Parser failed with error
This message can be inappropriately displayed when you have entered an incorrect address in the URL box. The appropriate error message should read similarly to the following one:
[nQSError: 46121] is not a correct URL
To work around this issue, ensure that you enter the correct URL.
[nQSError: 64001] The file not found
This message can be inappropriately displayed when the file that you are importing does exist but is not well formed. To work around this issue, ensure that the file exists, that the file is well-formed, and that all tags in the file are in the proper order and syntax.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
You might see an error message that Oracle BI Server is not running under the following situation. You have been working in online mode within the Administration Tool, Oracle BI Server is restarted without the repository or the Administration Tool being closed, and you try to reopen the repository in online mode.
To work around this issue, close the Administration Tool and reopen the repository in online mode.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
When users run a query against data from SAP/BW (Business Information Warehouse), they might see an error message. If the connection has timed out, then this fact is not reflected in the resulting error message.
This issue has no workaround.
This issue applies to version 10.1.3.2. This issue is fixed in version 10.1.3.2.1.
You might encounter the following issue for users defined within the repository. If an initialization block tries to change the USER system variable, then the initialization block does not execute. Other session variables within the same initialization block are also not set. This issue does not occur if the users are not stored within the repository.
To work around this issue, separate the initialization block into two different initialization blocks, one to get or set the USER system variable and the other to get or set the other session variables.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
If you perform the following steps, you might cause Oracle BI Server to crash:
Import a new physical schema into the repository.
Delete all existing physical, business model, and presentation objects.
Save the changes.
This issue has no workaround.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
With an IBM DB2 database on the IBM OS/390 and AS/400 operating systems, the TIMESTAMPDIFF function is translated into SQL that approximates the values that the function is processing. This approximation can cause incorrect values to be returned. This issue has no workaround.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
Chapter 11 of the Oracle Business Intelligence Server Administration Guide contains a section called "Configuring Query Caching." The first two paragraphs for that section should be replaced with the following text:
The query cache is enabled by default. After deciding on a strategy for flushing outdated entries, you should configure the cache storage parameters in the NQSConfig.INI file. This section includes information on the tasks necessary to configure the Oracle BI Server for query caching. For details about the parameters used to control query caching, see Oracle Business Intelligence Infrastructure Installation and Configuration Guide.
This section provides release notes for Oracle Business Intelligence Presentation Services (Oracle BI Presentation Services). It contains the following topics:
Section 4.2, "Catalog Manager Appears Slow to Open Catalogs"
Section 4.3, "Advanced Search Fields Might Appear Missing in Catalog Manager"
Section 4.4, "Changing Permissions for Multiple Objects in Catalog Manager"
Section 4.5, "Managing Groups and Users Dialog Contains Incorrect Information"
Section 4.6, "Attempts to Copy and Paste Content Might Not Work if Replace is Not Selected"
Section 4.7, "Changing the Report Path for a Portlet Might Not Update the New Path Correctly"
Section 4.8, "Device Numbers for iBots Require Standard Strings"
Section 4.10, "Virtual Memory Growth on Windows XP Machines"
Section 4.11, "Issue Opening Reports with Non-ASCII Names on Windows 2000 Machines"
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
You can take ownership of another user's folder in Catalog Manager. After taking ownership, you might notice that the properties of the folder continue to display System Account as the owner. To work around this issue, select the parent folder and select the Refresh option on the View menu.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
When you open a Presentation Catalog in Catalog Manager, you will not see the cursor changing to indicate that the catalog is being opened. The time required to open a catalog depends on various factors, including the size of the catalog.
If you enter an incorrect path for the catalog, then you might wait several moments before seeing an error message about the incorrect path.
These issues have no workaround.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
You might notice missing fields in the Advanced Search area within Catalog Manager. This situation occurs when you toggle between the Explore mode and the Search mode after expanding the Advanced Search area. If fields appear to be missing, then click the Expand icon (a right-facing triangle) next to the Advanced Search text to display the complete option list.
This issue has no workaround.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
You can select multiple objects in the Catalog Manager tree. If you select multiple objects and try to edit the permissions of those objects, then the Catalog Manager edits the permissions only for the first object in the tree. You cannot edit permissions for more than one object at a time.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
The Edit Catalog Group dialog makes the following statement: "The table below contains a list of the current members of this group. Users can join the group by entering the group's password from the 'Join Catalog Group' screen, or you can manually add them by clicking Add New Member below."
The ability to associate an account to a group has been removed. Disregard this statement on the Edit Catalog Group dialog.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
When you copy content from one Presentation Catalog to another, you have the option to replace existing files when the same folder exists in the destination catalog as in the original one. If you choose to not replace existing files, then no content is copied to the destination catalog, whether that content is new or previously existing.
To work around this issue, individually copy new folders and files to the destination catalog.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
When you set up portlets for a portal client, you must specify the report path to the content to be displayed. If you try to change the report path later, the system might not accept a change to a previously saved portlet. To work around this issue, completely remove the existing portlet and create a new portlet with the correct report path.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
You can use iBots to allow users to select a device to which the system can send an alert. When a user is entering a number for a device such as a phone, pager, or handheld computer and enters characters other than numbers, the user might notice an error message. To work around this issue, users should enter numbers that contain only digits and not other characters such as periods, hyphens, and parenthesis.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
If you use HTML to mark up reports and dashboards, then you might see the HTML tags in the application. The appearance of these tags is likely related to the setting of the HardenXSS element. The default setting of the HardenXSS element was changed in this release as a part of a larger effort to provide more secure Web applications. The HardenXSS element is intended to discourage cross-site scripting attacks and is now enabled by default.
To work around this issue, disable the HardenXSS element as described in the Oracle Business Intelligence Presentation Services Administration Guide.
This issue applies to version 10.1.3.2. This issue is fixed in version 10.1.3.2.1.
With specific testing configurations on Windows XP machines, it was observed that the virtual memory of Oracle BI Presentation Services did not stabilize and did continue to grow. If you encounter such a situation, then enable the XPLowFragmentationHeap setting to resolve this condition and to allow virtual memory stability. Set the XPLowFragmentationHeap element to True in the ServerInstance element of the instanceconfig.xml file.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
If you download a report that has a non-ASCII name and you attempt to open the report directly from the Save dialog, then you might see a blank report on a Windows 2000 machine. Windows 2000 might have difficulty opening the file due to the inline file name conversion.
To work around this issue, either rename the file to have a name that contains ASCII characters or save the name to the local machine first, then attempt to open the file.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
A practical limit exists for the inclusion of Oracle BI portlets within a portal. A variety of factors including report complexity, server memory and CPU, and configuration affect performance. As a general rule, keep the number of distinct portlets served by Oracle Business Intelligence Suite Enterprise Edition to five or less. For the inclusion of larger blocks of content, you can incorporate entire Interactive Dashboards or individual dashboard pages into a portal as a single unit.
This section provides release notes for Oracle Business Intelligence Answers (Oracle BI Answers). It contains the following topics:
Section 5.1, "Refreshing Before Downloading in Compound Layout View"
Section 5.2, "Defining an Aggregation Rule for a Set Operation"
Section 5.4, "Formatting Labels for Columns with Aggregations Might be Inoperable"
Section 5.6, "Session Times Out When Publishing Oracle BI Content to OracleAS Portal"
Section 5.7, ""Resource Not Found" Error Message When Publishing Oracle BI Publisher Content"
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
As you work in the Compound Layout View, you can change the output by modifying the different views. Before selecting the Download link on the bottom of the page, select the Refresh Results icon. By refreshing first, you ensure that any recent changes are reflected in the downloaded views.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
When you use a set operation, ensure that you define an aggregation rule. If you use the default aggregation, then the expression does not work with set operations.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
As you work in the Formula Editor dialog for a column, you can select an existing column in the formula (by highlighting it) and you can replace it with another column from the column picker. However, when you use certain browser versions, you cannot replace the highlighted column with the new column. To work around this issue, delete the current column before adding the new column.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
When you add an aggregation to a column in a pivot table, you might find that certain formatting features on the Format Labels options page for totals are not working. This issue has no workaround.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
If the Report-Based Total option is not selected, then you might find that filtering on nested aggregates returns the same result as when the Report-Based Total option is selected. This issue has no workaround.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
When you use OracleAS Portal to publish Oracle BI content, you might notice that the portlet session expires. To work around this issue, use the ClientSessionExpireMinutes element in the instanceconfig.xml file to increase the length of the session.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
If you notice a "Resource Not Found" error message when attempting to publish an Oracle BI Publisher report to an Oracle BI Dashboard, then the cause is likely a reference to a report with a long name, such as one with 28 or more characters. In these cases, you can work around the issue by republishing the report using a shorter name.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
If an error message or a graphic that contains an "X" in place of a chart appears in a report that was downloaded as MHTML, then the cause likely involves the way that the browser is interpreting the MHTML format. Problems most often arise when opening the MHTML report directly.
To work around this issue, first save the MHTML output as a file, then open that saved file.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
The Oracle Business Intelligence Answers, Delivers, and Interactive Dashboards User Guide incorrectly identifies the position of the format mask when describing the syntax for using variables. The syntax should be changed in the following topics.
In the topic entitled "What is the syntax for referencing repository and presentation variables?'", the bullet points should read as follows:
@{<variableName>}[format] - for repository variables. For example, @{dashboard.path} inserts the path to the current dashboard.
- @{variables.<variableName>}[format]{<value>} - for presentation variables. For example, @{variables.myFavoriteRegion}{Central} inserts the value of the presentation variable myFavoriteRegion.
variables - prefix that is required when you reference a presentation variable in a request.
variableName - a reference to an object available in the current evaluation context. For example: @{variables.myFavoriteRegion}.
format (optional) - a format mask (applied to {<variableName>}), dependent on the data type of the variable. For example: #,##0, MM/DD/YY hh:mm:ss, and so on.
value (optional) - a constant or variable reference indicating a value to be used if the variable referenced by the variableName is not populated (that is, is undefined).
In the topic entitled "To add or modify an Oracle BI narrative view", the syntax descriptions in the rows entitled "Prefix", "Narrative", and "Postfix", should each read as follows:
You can use the @{variableName}[format]{<value>} syntax to include a variable.
In the topic entitled "To add or modify an Oracle BI static text view", in the table row entitled "Variables", the first sentence should read as follows:
The following HTML example includes variable expressions using the @{variableName}[format]{<value>} syntax:
There are no known issues for Oracle Business Intelligence Interactive Dashboards (Oracle BI Dashboards).
This section provides release notes for Oracle Business Intelligence Delivers (Oracle BI Delivers). It contains the following topics:
Section 7.1, "iBot Headlines Cannot Contain Backslash Characters"
Section 7.4, "Issue with Conditional iBots, Unions and Filters"
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
When you create a headline for an iBot, do not include the backslash (\) character in the headline. If the headline contains a backslash character, then you might see a fatal Oracle BI Presentation Services error in the Job Manager.
This issue has no workaround.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
Under certain circumstances, if an iBot cannot connect to a database to run the query for the content, then the iBot recipient might receive an email that contains an ODBC error message.
This issue has no workaround.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
When you create an iBot on a Dashboard page that contains prompts, you cannot set values for the prompts prior to the iBot running.
This issue has no workaround.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
When you create a conditional iBot, be aware that it cannot be based on a request that contains both a union query and a filter. If you create such an iBot, you will see an error message in the scheduler log, but nowhere else. This issue has no workaround.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
In a clustered environment, an iBot that runs multiple instances of a report that is personalized for individual users will run on a single server. If the server goes down during an iBot run, then the iBot is scheduled to re-start automatically. If the server continues to be unavailable and the number of iBot re-start attempts exceeds the "Number of Request Tries" parameter, then a log file entry is generated.
This issue has no workaround.
This section provides release notes for Oracle Business Intelligence Disconnected Analytics (Oracle BI Disconnected Analytics). It contains the following topics:
Section 8.1, "Path Not Found Error Message on Mozilla Browser"
Section 8.2, "Incremental Preprocessed Synchronization Issues on Linux System"
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
If you access the Oracle BI Disconnected Analytics page using a Mozilla browser, then you might encounter a "Path Not Found" error when you select the Add/Edit Filter option. To work around this issue, use a browser other than a Mozilla one.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
If Oracle BI Presentation Services runs on a Red Hat Linux machine, you might encounter issues when performing an incremental preprocessed synchronization. This issue has no workaround.
This section provides release notes for Oracle Business Intelligence Publisher (Oracle BI Publisher). It contains the following topics:
Section 9.1, "JDK 5.0 Bug Affects Performance of Oracle BI Publisher"
Section 9.3, "Sorting Within a Nested For-Each-Group Fails with EmptyStackException Error"
Section 9.4, "PDF Form Processor Lacks Support for Landscape Template for Repeatable Fields"
Section 9.6, "Alternate Table Rows Formatting Not Working in HTML, RTF, and Excel Outputs"
Section 9.7, "Header and Footer Margin from Edge Not Preserved in RTF Output"
Section 9.9, "CUPS Server Does Note Appear as a Delivery Destination in Clustered Environment"
Section 9.11, "Concatenated Data Sources Do Not Load Properly to the Template Builder"
Section 9.12, "Schedules Tab and Buttons Disabled Until the Scheduler is Properly Configured"
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
There is a bug in Java SE Development Kit (JDK) 5.0 version 1_5_0_7 that impacts the performance of Oracle BI Publisher. For better performance, upgrade to JDK 5.0 update 11 (1_5_0_11). Download and install this update from the following location:
http://java.sun.com/javase/downloads/index_jdk5.jsp
After installing the JDK update, you must modify the OC4J start-up script or batch file to point to the new JDK location.
To modify the OC4J start-up script
On Windows, open <OracleBI>\oc4j_bi\bin\oc4j.cmd for editing. On Linux or UNIX machines, open $OracleBI\setup\oc4j.sh for editing.
Set the JAVA_HOME variable to point to the new JDK location. For example, JAVA_HOME=D:\Program Files\Java\jdk1.5.0_11.
If you installed Oracle Business Intelligence Presentation Services using the Basic Install option on the machine where JDK has been updated, you must modify the instanceconfig.xml file to point to the new JDK location:
To modify the instanceconfig.xml file
Open the <OracleBIData>/web/config/instanceconfig.xml file for editing.
Set the JavaHome parameter to the point to the new JDK location. For example, <JavaHome>D:\Program Files\Java\jdk1.5.0_11</JavaHome>.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
If scroll bars or a report appear clipped when you have an Oracle BI Publisher report embedded in a dashboard, then you might need to increase the height property of the object on the dashboard page. Edit the properties of the Oracle BI Publisher object on the dashboard page and try a height setting greater than 550 pixels until you find one that correctly displays the entire report and the scroll bar controls.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
You can sort a group of data values using the <?sort:element_name?> syntax. This syntax follows immediately after the for-each-group syntax. This sort syntax does not work when it is included under a nested for-each-group. If you include this sort syntax under a nested for-each-group, then you will notice an EmptyStackException error and the report output is not displayed.
This issue has no workaround.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
When you create PDF output in Portrait mode with repeatable fields, the report output is correctly formatted. However, when the same report is created in Landscape mode, the table headers are correct but the following occurs:
Repeating line information (that is, each data field in the iteration) rotates by 90 degree.
The repeating lines spread across in a horizontal direction from right to left instead of top to bottom in a vertical direction.
This issue has no workaround.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
The RC4 algorithm is less secure than newer algorithms such as AES and is not recommend for use in new applications. However, the RC4 algorithm is the only supported encryption algorithm for Adobe Acrobat 6.0. Support for AES encryption for Adobe Acrobat 7.0 and higher versions is planned for future releases of Oracle BI Publisher.
This issue has no workaround.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
The user guide contains the "Row Formatting" topic that describes how to set the background color on alternate rows in a tabular report. This description works for PDF output only. In HTML, RTF, and Excel output formats, the alternate rows do not show the background color. In these output formats, all the rows appear with a white background.
This issue has no workaround.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
Microsoft Word provides a Page Setup option for specifying the margin for the headers and footers from the edge of the page. This option is available by choosing the File menu, then Page Setup, then the Margins tab, and the From edge box. This margin setting is not retained when the output format is RTF. The output is created with the default margin settings instead. The margin settings do work correctly for other output formats such as HTML, PDF, and Excel.
This issue has no workaround.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
As Oracle XDK conforms to XSL standards for IEEE 754, you might encounter rounding issues when adding numbers that are decimals. For example, suppose you add 13683.80 and 516.39, using this syntax in Oracle BI Publisher:
<?13683.80 + 516.39?>
The value returned is 14200.189999999999 which is a limitation based on the IEEE 754 Binary Floating-Point-Arithmetic.
To work around this issue, use the format-number function or the round syntax as shown here to obtain a return value of 14200.19:
<?format-number:(13683.80 + 516.39);'D99'?>
or
<?(round((13683.80 + 516.39)*100) div 100)?>
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
If you are using a clustered environment and you have a CUPS server implemented as a delivery option with no other printers defined, then you might not see the CUPS Server as a delivery option.
To work around this problem, add a real or dummy printer destination by creating an entry in the Admin > Delivery > Printer interface.
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
When viewing a report layout that has a chart in Excel output, you might not see the chart and will instead see only a small icon in the place where you expect the chart to be.
To work around this problem, you must unblock security on image URLs, as described in the follow steps:
Open the WEB-INF/web.xml file.
Find the following block:
<filter-mapping> <filter-name>SecurityFilter</filter-name> <url-pattern>/xdo/tmp/*</url-pattern> </filter-mapping>
Change the <url-pattern> element as shown:
<filter-mapping> <filter-name>SecurityFilter</filter-name> <url-pattern>/xdo/tmp/*.tmp</url-pattern> </filter-mapping>
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
If the data source is concatenated XML from multiple SQL queries, then the XML data will not load properly to the Template Builder from the direct connection to the BI Publisher server.
To work around this issue, after building the data model, generate sample data and save it to an accessible directory. Use the Template Builder's load data function (choose Oracle BI Publisher, Data, and Load Sample XML Data) to load the report data to the Template Builder. For more information on using the Template Builder in disconnected mode, see the Oracle Business Intelligence Publisher User's Guide.
This issue applies to version 10.1.3.2.1.
Starting with version 10.1.3.2.1, if the administrator has not correctly configured the BI Publisher scheduler, then the Schedules tab and the Schedule buttons will be disabled even when the user has the XMLP_SCHEDULER role. To enable the Schedules tab and the Schedule button, you must configure and install the Scheduler tables.
There are no known issues for Oracle Business Intelligence Scheduler (Oracle BI Scheduler).
This section provides release notes for Oracle Business Intelligence Administration Tool (Oracle BI Administration Tool). It contains the following topics:
This issue applies to versions 10.1.3.2 and 10.1.3.2.1.
If you want to use an XML file as a physical data source in Oracle BI Administration Tool, the file name in the URL that you specify must have an XML suffix. For example, if you have a data source located in D:\datasources\xml\Categories.xml, the value that you specify in the URL field on the XML tab of the Physical Table - <name of data source> dialog must be D:\datasources\xml\Categories.xml. In addition, you must select XML as the value in the Database field on the General tab of the Database dialog.
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
TTY Access to Oracle Support Services
Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.
Oracle Business Intelligence Suite Enterprise Edition Release Notes, Version 10.1.3.2
Part No. B31773-07
Copyright © 2007 Oracle. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.
