Table of Contents:
This document includes important, late-breaking information about this release of Oracle Essbase Administration Services. Review this Readme thoroughly before installing Administration Services.
For installation information, platform support and other Oracle Business Intelligence Enterprise Edition documentation, please see: http://www.oracle.com/technetwork/middleware/bi-enterprise-edition/documentation/index.html.
The following are the noteworthy defects fixed in this release:
8420324 -- Log Analyzer charts generated in Administration Services may contain duplicate entries.
13909220 -- The @RETURN function was not included in the list of functions displayed in Calculation Script Editor.
9476104 -- When you attempt to execute a calculation script on a database that is read-only (in archive mode), the error message generated is incorrect.
13653217 -- In the Assign Access Control dialog box, the context-sensitive Help button does not work.
14159520 -- When launching Administration Services, if the launch fails due to a failure to initialize the MaxL API, the error message generated does not indicate this.
13862154 -- When a calculation with a name containing an ampersand (“&”) is executing as a background process, it will display in the list of background processes as a blank row.
10195806 -- Attempting to launch Report Script Editor on a report script from under an application node within Enterprise View may fail, and no error message displays.
13326005 -- When using Administration Services to connect to Oracle Essbase and unable to connect, the error message generated is insufficiently detailed to assist in diagnosing and resolving the issue.
The following issues are the noteworthy known issues of this release.
13359958 -- When logging into an Administration Server configured under Oracle BI EE, you must specify the port number with the server name. For information on port settings, see the “Oracle Fusion Middleware Administrator's Guide”.
14364637 -- Using Administration Services Web Launch on a Windows machine running Java Runtime Environment (JRE) 1.7, logging onto Administration Services may fail. To work around this issue, disable JRE 1.7 and install or enable JRE 1.6:
Open Windows Control Panel, then Java.
Select the Java tab in the Java control panel.
Select the User tab.
In the table, in the Enabled column, enable only version 1.6
Click OK as needed to save your changes.
9791235 -- Searching for members using Outline Editor and the asterisk (*) wildcard may not retrieve the member or members. A similar search using Outline Viewer will succeed.
10101213 -- If you are running Administration Services Console in Windows 2008, you may not be able to create calculation scripts.
8459384 -- In the Simplified Chinese language version of Administration Services Console, log charts for errors and warnings are not displayed in Log Analyzer.
12673530 -- When running Administration Services Console under Windows 7, some functions may not work. If this occurs, changing Windows security so that the Users group has full access to the folder C:\Hyperion\products\Essbase\eas\console\temp (in a default installation) may resolve the issue.
12376259 -- When Oracle WebLogic Server is restarted after stopping Administration Server, Administration Services may not retain information on any Essbase servers added by the user.
13115255 -- If you attempt to preview data on an Essbase instance that has been specified in Administration Services Console as EssbaseCluster-1, the action may fail with the error message, Can’t connect to olap services. Can’t connect to Essbase server. Error:Essbase Error (1042003): Network Error (11001): Unable to locate [EssbaseCluster-1] in Hosts file.
When you cut and paste code snippets from a PDF file, some characters can be lost during the paste operation, making the code snippet invalid. Workaround: Cut and paste from the HTML version of the document.
In the topic "Setting the Timeout Period for Administration Services Sessions" in the Oracle Essbase Administration Services Online Help, the timeout period is incorrectly described as twenty-four hours. It should be 45 minutes. The English-language help has been corrected; translated help will still show this as 24 hours.
When an Essbase server is disconnected, options to create, edit, view, and generate Essbase server logs will be greyed out.
It is our goal to make Oracle products, services, and supporting documentation accessible to the disabled community.Oracle Essbase Administration Services supports accessibility features, which are described in the product's Accessibility Guide. The most up-to-date version of this guide can be found in the Oracle Business Intelligence Enterprise Edition Documentation Library on the Oracle Technology Network (http://www.oracle.com/technetwork/middleware/bi-enterprise-edition/documentation/index.html).
In addition, this Readme file is accessible in HTML format.