Table of Contents:
This document includes important, late-breaking information about this release of Oracle Hyperion Provider Services. Review this Readme thoroughly before installing Oracle Enterprise Performance Management System.
For new features relating to installation, architecture, and deployment changes in this release, see “New Features in this Release” in the Oracle Enterprise Performance Management System Readme.
Late-breaking information about the installation of EPM System products is provided in the Oracle Enterprise Performance Management System Installation and Configuration Readme. Review this information thoroughly before installing EPM System products.
Information about system requirements and supported platforms for EPM System products is available in spreadsheet format in the Oracle Enterprise Performance Management System Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on Oracle Technology Network (OTN):
Information about supported languages for EPM System products is available in spreadsheet format on the Translation Support tab in the Oracle Enterprise Performance Management System Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on OTN:
You can upgrade to EPM System Release 126.96.36.199 from the following releases:
Note: For upgrading instructions, see the Oracle Enterprise Performance Management System Installation and Configuration Guide, “Upgrading EPM System Products.”
Table 1. Supported Paths to this Release
|Upgrade Path From Release ...||To Release 188.8.131.52|
Apply the maintenance release to move to Release 184.108.40.206.
For Oracle Hyperion Financial Close Management, applying the maintenance release is supported only from Release 220.127.116.11 or 18.104.22.168.
For Oracle Hyperion Financial Management, applying the maintenance release is supported only from Release 22.214.171.124, 126.96.36.199, or 188.8.131.52.
Upgrade to Release 184.108.40.206 and then apply the maintenance release to move to Release 220.127.116.11.
Release 18.104.22.168.x to 22.214.171.124.x
Apply the maintenance release to move to Release 126.96.36.199, upgrade to Release 188.8.131.52, and then apply the maintenance release to move to Release 184.108.40.206.
Caution! Oracle recommends using the same version of all Oracle Essbase portfolio products (Essbase, Oracle Essbase Administration Services, Provider Services, and Oracle Essbase Studio) and components (server, client, runtime client, API, and JAPI).
This section includes defects fixed in Release 220.127.116.11.000. To review the list of defects fixed between earlier releases, use the Defects Fixed Finder. This tool enables you to identify the products you own and your current implementation release. With a single click, the tool quickly produces a customized report of fixed-defect descriptions with their associated platforms and patch numbers. This tool is available here:
19347528 -- Oracle Smart View for Office times out and returns the following error message: “Cannot connect to the provider. Make sure it is running in the specified host/port.”
18596386 -- Need to add a JAPI to support a new Essbase API to pivot multiple POV members.
18154734 -- In Smart View, when using HsDescription, member names are case sensitive.
17997117 -- Provider Services writes empty member attributes even when not requested by Smart View, resulting in performance degradation.
17570022 -- Dragging multiple members from the POV toolbar into the Smart View Ad-hoc sheet does not work.
17505060 -- Empty rows are inserted in a Smart View retrieval even when Formula Fill is turned off.
16023006 -- Attempting to expand a member in the Smart View Member Selection Dialog results in the following error message: "Provider Services has encountered an unexpected Essbase Server error."
19361057 -- Only one selected member in the POV is populated when multiple Dimension Members are dragged onto the ADHOC reporting sheet from the POV.
19829466 -- Pivoting multiple members to POV toolbar is not working as expected.
18085424 -- JAPI was returning the error message, "Not a valid entry." This error message was not adequately informative, so it was updated to "Unrecognized Essbase Error [%s]. Check Essbase logs for details."
17934553 -- JAPI does not read a data load rules file.
The following are the noteworthy known issues of this release.
22596350 -- Drill-through reports with recursive hierarchy based cube deployments from Oracle Essbase Studio do not work if Dynamic Time Series functions exist in the Oracle Smart View for Office grid.
8674073 -- In Smart Slice dimensions that contain more than 5000 members, not all members will be displayed when users zoom in on the dimension. To use Smart Slices on dimensions with more than 5000 members, in the essbase.properties file, located in EPM_ORACLE_INSTANCE\bin, set the property service.olap.dataQuery.grid.maxRows=0 and increase maximum heap size to 512M. Restart Provider Services.
11655006 -- Ensure that you use the correct syntax to specify secure mode. When you set the OLAP_NAME to cluster URL, use the values “yes” or “no” to specify whether you want to use secure mode, for example, OLAP_SERVER=http://<servername>:<port>aps/Essbase?ClusterName=Win32Cluster-1&SecureMode=yes
All other values (for example, SecureMode=true or SecureMode=false) are invalid and are interpreted by Provider Services as SecureMode=no.
If you use invalid syntax, no error message is generated, nor is the connection halted. Therefore, if you were to enter SecureMode=true to specify secure communication, it would be interpreted as SecureMode=no, and the connection would be made successfully but not in secure mode.
11898620 -- When you use the Essbase cluster URL in a Java API client program running in 3-tier APS mode, the Provider Services host used to resolve the Essbase cluster URL is the Provider Services host name to which the client is connected in the 3-tier mode; the Provider Services host name within the Essbase Cluster URL is not used. These two references to Provider Services hosts are usually same. When you use the Essbase cluster URL in a Java API client program running in embedded 2-tier mode, then the Provider Services host used to resolve the Essbase cluster URL is the Oracle Hyperion Provider Services host name within the Oracle Essbase cluster URL.
Find the latest EPM System product guides in the Oracle Help Center (https://docs.oracle.com/en/). To access documents to view or download, click the Applications icon. In the Applications Documentation window, select the EPM tab, and then click the Enterprise Performance Management link.
You can also find deployment-related documentation on the Oracle Technology Network (http://www.oracle.com/technetwork/index.html) and on the Oracle Software Delivery Cloud website (http://edelivery.oracle.com/EPD/WelcomePage/get_form). Or you can visit the EPM System Documentation Portal (http://www.oracle.com/us/solutions/ent-performance-bi/technical-information-147174.html). There, you’ll find links to My Oracle Support, EPM Supported Platform Matrices, and more.
Some tables and text may display incorrectly in online help when using Internet Explorer 9.
Send feedback on product documentation to the following email address:
Follow EPM Information Development on these social media sites:
Twitter - https://twitter.com/HyperionEPMInfo
Our goal is to make Oracle products, services, and supporting documentation accessible to the disabled community. EPM System products support accessibility features, which are described in the product's Accessibility Guide. Find the most up-to-date version of this guide in the Oracle Enterprise Performance Management System Documentation Library on the Oracle Technology Network (http://www.oracle.com/technology/documentation/epm.html).
In addition, this Readme file is accessible in HTML format.