Readme
Supported Paths to this Release
Defects Fixed in Release 11.1.2.0
This document includes important, late-breaking information about this release of Oracle Essbase Studio. Review this Readme thoroughly before installing Essbase Studio.
See the Oracle Essbase Studio New Features guide.
For new features relating to installation, architecture, and deployment changes in this release, see “New Features” in the Oracle Hyperion Enterprise Performance Management System Installation Readme.
Late-breaking information about installation of EPM System products is provided in the Oracle Hyperion Enterprise Performance Management System Installation Readme. Review this information thoroughly before installing EPM System products.
If you use Essbase Studio with Enterprise Performance Management Architect, after the installation and configuration of Enterprise EPM Architect 11.1.2.1.000, you must install EPM Architect patch 11804477.
Information about system requirements and supported platforms for EPM System products is available in a spreadsheet format in the Oracle Hyperion Enterprise Performance Management System Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on the Oracle Technology Network (OTN) and listed in the Oracle Business Intelligence product area:
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
Information about supported languages for EPM System products is available in a spreadsheet format on the Translation Support tab in the Oracle Hyperion Enterprise Performance Management System Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on OTN (listed in the Oracle Business Intelligence product area):
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
<Shannon's update for July 2011 is input below. // Shannon's updates are input through 3/8/2011>You can upgrade to EPM System Release 11.1.2.1 from the following releases:
Note: For instructions to upgrade, see the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide, “Upgrading EPM System Products.”
|
Release Upgrade Path From |
To |
|
11.1.2.0.x |
11.1.2.1 Note that when moving from Release 11.1.2.0.x to Release 11.1.2.1, you use the "Apply Maintenance Release" option in EPM System Installer, instead of following the documented upgrade procedures. |
|
11.1.1.3.x |
11.1.2.1 |
|
An environment that includes multiple releases, which can include an environment with one instance of Shared Services or an environment with two instances of Shared Services |
See “Upgrading from an Environment with Multiple Releases” in the "Upgrading EPM System Products" chapter in the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide. |
· If you are starting from Release 11.1.1.x, Oracle recommends the following upgrade path: 11.1.1.0 or 11.1.1.1 or 11.1.1.2 to 11.1.1.3 to 11.1.2.1
· Security Synchronization between Essbase and Shared Services was removed in Essbase Release 9.3, starting with Release 9.3.1.4.1. Essbase and Shared Services Release 11.1.1.3, however, still synchronize security information. For this reason, if you are using Essbase Release 9.3.1.4.1, 9.3.1.5, 9.3.1.6, or 9.3.1.7, you must first upgrade all products to Release 9.3.3, as recommended above. Upgrading to Release 11.1.1.3 is not an option for these Essbase releases.
|
Defect Number |
Description of Fix |
|
• 9167759 |
In Essbase cubes that support duplicate member names, drill-through now succeeds when performed on a member where the key binding is different from the caption binding. |
|
• 9290430 |
When using the MaxL Deploy command, cube redeployment succeeds in incremental update mode when more than 100 rules are generated for a non-Unicode mode application. |
|
• 9294660 |
Cubes containing varying attribute associations now deploy successfully when an incremental load option is selected. |
|
• 9404788 |
In minischemas based on MySQL data sources, you may now add joins manually (that is, using the mouse to drag a join line) as follows: Between a user-defined table and a source table when the two columns to be joined are both of type "int" (integer). Between a user-defined table and a source table when the two columns to be joined are both non-integer type columns, such as varchar or datetime. |
|
• 9437201 |
When deploying cubes from EPM Architect, formulas associated with dimensions, as well as members, now successfully deploy to Essbase. |
|
• 9468571 |
When creating aliases by inspection, note that the search criteria you enter in the "Pattern for alias columns" text box is case-sensitive. For example, if alias columns in your data source are suffixed with the pattern, "_ALIAS," uppercase, then you must enter "*_ALIAS" in order to locate those columns. |
|
• 9468594 |
When creating aliases by inspection, the list of data source connections from which you can choose no longer contains all existing connections. Now, only connections to relational sources and text file sources are displayed. |
|
• 9488483 |
In minischemas based on flat file data sources, joins can be deleted and added back again without error. |
|
• 9488558, 9492822 |
When working with recursive hierarchy drill-through, the drill-through report is now properly populated when you specify drill-through by generation. |
|
• 9491559, 9492822 |
When working with recursive hierarchy drill-through, if you specify drill-through by level and provide a level number, users are now able to drill through only on the level you specify, and not on all levels. |
|
• 9509346 |
In the Connection Wizard, the Back and Next buttons now take you to the correct wizard page. Note: If you use the Back button to return to the Define Parameters page of the wizard, and then rename the connection, you must select the tables for the connection in the Select Tables page, choose a minischema option in the Select Minischema page, and so forth. |
|
• 9788628 |
Essbase Studio was unable to correctly load measures dimensions that contained more than 512 members. To correct this problem, Essbase Studio now generates a rules file for every 250 members in a measures dimension. For example, if a measures dimension contained 715 members, Essbase Studio would generate three rules files: two rules files containing 250 members each, and one rules file containing 15 members only. |
|
• 9793221 |
Essbase models may now contain a measure hierarchy that includes user-defined members. The model may be of aggregate or block storage type, and "Duplicate member name support" may be selected or cleared for either storage type. |
|
• 9840885 |
In the Essbase model, the ASO Storage Options "Store" and "Dynamic" are now available for user-defined dimensions and user-defined hierarchies, such as an alternate user-defined hierarchy, within a dimension. Note, however, that the "External Source" option is not available. |
|
• 9858242 |
When Oracle is used as the catalog database, Essbase Studio Server automatically attempts to reconnect to the Oracle database server if the physical connection is terminated by Oracle in either of these ways: · If the Oracle database server machine is rebooted after starting Essbase Studio Server. · If the Oracle database terminates the Essbase Studio Server connection because of a database timeout. |
|
• 10022413 |
There are no longer delays bringing up the Cube Deployment Wizard when redeploying models that have a large deployment history. |
|
• 10113981, 10191522 |
When deploying applications from EPM Architect, shared members are now correctly loaded into Essbase. |
|
• 10236883 |
After deployment, cubes enabled for XOLAP now correctly display any text entered in the "Name in Cube" field in the model. |
|
• 10239766 |
In order to comply with the parameters an incremental load, the following options in the Cube Deployment Wizard are enabled/disabled accordingly: · If the "Incremental Load" option is selected, then the "Delete all members first" option is disabled. · If the "Delete all members first" option is selected, then the "Incremental Load" option is disabled. |
|
• 10270537 |
<2/22-approved>Multi-column joins created using the "Edit Properties of Minischema Join" dialog box were not saved to the Essbase Studio catalog when the minischema was saved and, therefore, were not visible upon reopening the minischema. |
|
• 10278443 |
<2/22-approved>In Essbase applications deployed from EPM Architect, if any accounts dimension member contained a single quote or apostrophe (such as in a member named “KPI's”) on the EPM Architect side, Essbase Studio failed to deploy the application to Essbase. Essbase Studio now properly handles these member names. |
|
• 10404119 |
<2/22-approved>Essbase Studio Server can now handle deployment, without timing out, of Essbase applications from EPM Architect where the accounts dimension is particularly large (for example, containing more than 2,000 members). |
|
Defect Number |
Description of Fix |
|
• 6590022 |
Essbase Studio now correctly builds multichain hierarchies where two chains contain identical member names appearing in the same order, but the members come from different tables or different data sources. |
|
• 7136666 |
Microsoft SQL Server database names that start with a number were not supported prior to this release. For example, the database names, 12studiocat or 321salesdata, were not supported. |
|
• 7186683 |
An error occurred when attempting to open a saved relational-type drill-through report after changing the data source connection name on which it was based. |
|
• 7316865 |
After deployment of aggregate storage-enabled models in Essbase Studio (or Essbase ASO-enabled applications in EPM Architect), the hierarchy settings and data storage type were not correctly reflected in the subsequent Essbase outline. |
|
• 7321401 |
Data load from a text file data source was not working when the outline was built from an EPM Architect data source. |
|
• 7511541 |
If you remove a member from a measure hierarchy, and the same measure hierarchy exists in the Context tab of a drill-through report, the change made to the measure hierarchy is correctly reflected in the drill-through report definition when next opened in the drill-through report editor. |
|
• 7527828 |
In the Essbase Properties dialog box, Member Formula tab, the "From External Source" option was disabled, and was enabled only after applying changes, then saving, closing, and reopening the dialog box. |
|
• 7646767 |
When deploying a block storage-type Essbase model based on a "Dimension server" data source (EPM Architect), the Expense Reporting properties were not being sent to Essbase. |
|
• 7707818 |
Renaming alias sets was not working correctly and renamed alias sets were not properly reflected in the Essbase models in which they were being used. |
|
• 7832722 |
Essbase model validation was not being performed on custom prefixes in the Alias tab, causing errors during cube deployment. |
|
• 8355097 |
When the Essbase model was set to aggregate storage, options on the Info tab were enabled in error on the parent level of parent-child hierarchies, causing incorrect aggregations in the resulting outline. In the case of parent-child hierarchies, the options on the Info tab must only be enabled on the child level. |
|
• 8355228 |
After deployment of an aggregate storage-type Essbase model that supports duplicate member names and contains a parent-child hierarchy, shared members were not created. |
|
• 8481123 |
Essbase models containing calendar hierarchies were allowed to be created as block storage models in error. Now, when a cube schema contains a calendar hierarchy, the aggregate storage option in the subsequent Essbase model is automatically selected and cannot be cleared. |
|
• 8484071 |
When loading varying attributes, if Essbase encountered an unknown value (that is, a value that does not exist in the dimension) in the column that is mapped to either the "From" or the "To" field, Essbase failed. |
|
• 8488595 |
The English version of the Essbase Model page of the Preferences dialog box was displayed for all languages. The localized version was not displayed for any supported language. |
|
• 8528258 |
Drill-through to an Oracle BI EE URL did not work for member names containing spaces (multi-word member names). |
|
• 8533319 |
In the Connection Wizard, the default port number was not properly restored upon re-selection if it had previously been cleared and a different port number was input. |
|
• 8533869, 8533694 |
The Properties option is now disabled when the "Root" node (or folder) in the Metadata Navigator is selected. Note that the Root folder is not editable. |
|
• 8540675 |
In the Cube Schema Wizard, the Preview All hierarchy's functionality was not correctly displaying all hierarchy members. |
|
• 8600557 |
Essbase Integration Services catalog migration failed when the catalog data source to migrate to was a Microsoft SQL Server database. |
|
• 8612877 |
When concatenating the MonthShortName function by, for example, appending an underscore character to the end of the expression, extra spaces and garbage characters were added to the end of the strings displayed in the sample data. |
|
• 8627341 |
When attempting to perform a data load from multiple flat files (which is not supported), the load was unsuccessful, however, no error message or other indication of this was provided. |
|
• 8742674 |
During configuration, when an Oracle Service Name was provided for the Essbase Studio catalog, the syntax for the catalog.url property was not properly formed in the server.properties file, and Essbase Studio Server then failed to start. |
|
• 8810015 |
Any left outer joins created would disappear after closing and reopening the minischema. |
|
• 8810288 |
Joins created in Japanese versions of Essbase Studio were not properly displayed after closing and reopening the minischema. |
|
• 8900102 |
The MaxL "deploy" command was not working when issued from a MaxL Shell running on the 64-bit version of IBM AIX 5.3. |
|
• 9125476 |
Member names were being truncated at 34 characters, even though 80 characters is the limit. |
The following issues are the noteworthy known issues of this release.
|
Defect Number |
Known Issues |
|
N/A |
Integration Services catalog migration is not supported on 64-bit UNIX platforms or on the Windows 2008 64-bit platform. |
|
N/A |
Oracle Essbase Spreadsheet Add-in for Excel works in native locale. If Spreadsheet Add-in does not receive data in native locale, drill-through on cubes built in Essbase Studio is not supported. |
|
N/A |
Transformation rules defined in the Essbase model will not be used in query generation for drill-through operations. Workaround: You may edit the expressions for the dimension element's caption binding to transform members. |
|
N/A |
This needs to be added to the Studio doc in PS2If Oracle is your catalog database: Essbase Studio no longer issues the ALTER SYSTEM command when connecting to the catalog database. For increased performance, add the ALTER SYSTEM statement to the Oracle database user's privileges for the Essbase Studio catalog user. Following are the recommended settings: ALTER SYSTEM SET open_cursors=300 SCOPE=MEMORY The catalog user is specified in the server.properties file during configuration and should have the privileges necessary to execute the ALTER SYSTEM statement. |
|
6576813 |
The JISX0213 Japanese character set, which replaces the JISX0208 and JISX0212 Japanese character sets, is supported on Windows Vista. The Essbase family of products does not support the JISX0213 Japanese character set. |
|
7138321 |
You cannot deploy an XOLAP-enabled Essbase model that is based on an Oracle BI EE data source. |
|
7366645 |
<Keep as known issue in ps1>When using Hyperion Smart View or Essbase Spreadsheet Add-in to query cubes built in Essbase Studio, if the intersection for a drill-through cell is represented by both a base member and one or more associated attribute members, you cannot perform drill-through on that cell. Specifically, drill-through will not work on an intersection (cell) that is represented by members of a base dimension and members of attribute dimensions. When specifying intersections for a drill-through report in Essbase Studio, do not specify both the base and attribute hierarchies from a multichain hierarchy. Select only one of the hierarchies for drill-through. If you require drill-through from an intersection containing a base member and attribute members, you must build the cube using Essbase Integration Services. |
|
7665495 |
<this needs to be added to the doc in PS2>A 255-character limit applies to certain objects that you name in Essbase Studio. These objects are: · Data source connection names · User-defined table names · Metadata element names, such as dimension elements and hierarchies · Alias sets · Cube schema names · Drill-through report names These are the limits on Essbase application and database names: · 8-bytes for non-Unicode · 30-characters for Unicode |
|
8661977 |
<Keep as known issue in ps1>When deploying a cube for the first time, and the cube contains text or date measures, the data is loaded correctly. Upon subsequent deployments of the cube, selecting the "Load data" option along with either the "Add to existing data" or "Subtract from existing data" option, results in incorrect data. Workaround: Use custom data load SQL to selectively load data on numeric measures only, omitting any text or date measures. |
|
8897922 |
<Keep as known issue in ps1>When migrating an OLAP metaoutline from Essbase Integration Services to Essbase Studio, members in a hierarchy may not be sorted properly in the deployed Essbase cube if both transformation and sorting rules are defined on the original Integration Services member set. In Essbase Studio, performing transformation in Essbase Model Properties does not resolve the issue. Workaround: Perform transformation in the Dimension Element Properties dialog box by editing the key binding expression of the dimension elements. |
|
8908738, 7127257 |
<Keep as known issue in ps1>Microsoft Windows authentication is not supported for data source connections to Microsoft SQL Server. |
|
9196670 |
<Keep as known issue in ps1>Re-importing the catalog fails when the catalog was cleared by deleting objects in the Essbase Studio Console. Workaround: In the console, after deleting objects in the Metadata Navigator and before attempting to re-import, be sure to also delete minischemas from the Minischemas tab of the Source Navigator and alias sets from the Alias Set Manager. |
|
9315569 |
<Keep as known issue in ps1>The labeling rules listed in the Editing Labeling Rules dialog box were not translated and appear in English for all languages. The Editing Labeling Rules dialog box is accessed from the Time Depth area of the Calendar Hierarchy dialog box, as described in "Defining Time Depth" in the Oracle Essbase Studio User's Guide. |
|
9325297 |
Varying attributes do not support NULL values in the "FROM" or "TO" columns of the "history" table. When working with varying attributes, if the history table contains rows with a NULL value in either the FROM or TO columns, then the attribute values from these rows are not built into an attribute dimension. Workaround: Ensure that there are non-NULL values in the FROM and TO columns of the history table. For more information on history tables, see Working with Varying Attributes: Setting Up a History Table. |
|
9326364 |
<Keep as known issue in ps1>If two independent dimensions have the same leaf member name for one varying attribute, deployment fails with the error, "Duplicate name of the field in the query." For example, suppose there is a varying attribute dimension, "VAYRPER," and two independent dimensions, "Period" and "Year." If the leaf member name is the same for both "Period" and "Year" in the Essbase Model Properties, Independent Dimension Binding dialog box, the deployment will fail. Workaround: Rename the column for the physical relational table that will be used for the leaf member name. If that is not possible, you can create a user-defined table with the different column name and build the second independentÿdimension based on a column in the user-defined table. |
|
9364712 |
<Keep as known issue in ps1>When running Essbase Studio Server in nonstreaming mode (server.essbase.streamingCubeBuilding=False), deployment fails when the Essbase model is based on a Unicode data source. Workarounds: · Use streaming mode (server.essbase.streamingCubeBuilding=true). · Use nonstreaming mode (server.essbase.streamingCubeBuilding=false). Create a DSN and enable the N-CHAR support option as follows: o On Windows, use the ODBC Data Source Administrator to create a DSN with the "Enable N-CHAR Support" option selected. This option is found on the Advanced tab of the ODBC driver setup dialog box. o On UNIX or Linux, edit the odbc.ini file to create a new DSN, and set the EnableNcharSupport value as follows: EnableNcharSupport=1 See the Essbase Studio User's Guide for information on setting the server.essbase.streamingCubeBuilding property. |
|
9433391 |
<Keep as known issue in ps1, but these rules should be doc'ed in PS2>Deploying From Text File Data Sources ·
Cube deployment from text file data sources is always done in
nonstreaming mode, regardless of how the server property,
server.essbase.streamingCubeBuilding is set. · Cube deployment progress statistics are not supported on text file data sources. |
|
9477466 |
<Keep as known issue in ps1>In Smart View, when performing drill-through from an Essbase Studio-sourced cube to FDM, if the EPM System Single Sign-On token expires before the sessions of all products involved expire (Workspace, Analytic Provider Services, Essbase, Essbase Studio, FDM), the following message is displayed: "Error: An error occurred logging on to the system using single sign-on. Please contact your administrator. Error: 2067 - You do not have access to the application!" Workaround: Log in again to Workspace from Smart View client. |
|
9502269, 9492526 |
On Windows, when Essbase is started using OPMN, cube deployment fails for cubes built from Oracle Business Intelligence (OBI) data sources if the option "ODBC (Essbase dynamically creates ODBC connection string)" is selected in the Cube Deployment Wizard. Workarounds: For successful deployment, use one of the following workarounds: · In the Cube Deployment Wizard, specify an ODBC DSN for the OBI data source connection. See "Providing Connection Information for Cube Deployment" in the Essbase Studio User's Guide for more information. or · Start Essbase Studio Server in streaming mode, then perform the deployment. In streaming mode, the server.essbase.streamingCubeBuilding property is set to "true." See "server.essbase.streamingCubeBuilding" in the Essbase Studio User's Guide for information on this property. |
|
9561925 |
1/20/2011, Per Sergey, leave this in PS1 Known Issues Solaris only: Your machine likely has a network configuration problem if Essbase Studio Server fails to start, and either of the following messages appears in the server log file: · Cannot register server in catalog. · Network error prevented server registration check. Workaround: Manually add a single, empty row to the Essbase Studio catalog database table, cp_server_key. |
|
9578741 |
During cube deployment, if the Essbase model that is being deployed or its underlying data source contains MBCS (Multi-byte Character Set) characters, the OCI data source setting option is not supported. |
|
11663358 |
2/1, OK'ed by JosephCubes containing calendar hierarchies with day attributes do not correctly build during cube deployment as most of the day attributes are missing. (Related to bug 11696797.) |
|
11696797 |
2/1, OK'ed by JosephThe day attributes of a calendar hierarchy are not all listed under the hierarchy in the Essbase Model Properties dialog. (Related to bug 11663358.) |
|
11781604 |
If the machine name where Essbase Studio Server and Analytic Provider Server are hosted contains a period ( . ), the cube linkage for the cube must be manually reset after each redeployment before any drill-through reports can be executed from Smart View. Workarounds: · Before each redeployment, manually reset cube linkage as described in “Updating Cube Linkage for Individual Cubes.” or · Incorporate the ESSCMDQ commands below into a script solution that automatically resets the cube linkage after each redeployment. select <app> <db> getumc setumc <new umc string>
You can download the ESSCMDQ utility on Oracle Technology Network at the following location: http://www.oracle.com/technetwork/middleware/bi-foundation/esscmdq-sampleapps-093105.html |
|
11793745, 11830011 |
Drill-through reports cannot be displayed in Smart View for Essbase cubes deployed from Essbase Studio if the underlying Essbase model name contains non-ASCII characters. Workaround: In the Essbase Studio Console, ensure that Essbase model names contain only ASCII characters. |
|
12854605 |
<<Added this item for September 2011 update>>Due to internal Essbase model changes that were implemented in Release 11.1.2, when performing an upgrade from a pre-11.1.2 release to 11.1.2.1, if a model has varying attributes, it will not be upgraded correctly. Workaround: Before performing the upgrade, in the pre-11.1.2 environment, remove varying attributes from the Essbase models that contain them. After upgrade, recreate the varying attributes in the upgraded models. |
The Essbase Studio User’s Guide (PDF and HTML format) contains an appendix entitled “Essbase Studio Limitations and Guidelines,” which describes various limitations you may encounter while working with Essbase Studio.
Also, refer to the "Known Issues" section of this document for the latest information on limitations and guidelines.
If Essbase Studio Server fails to start, check the catalog.url property in the server.properties file to verify that the syntax is correct. If the syntax is incorrect, Essbase Studio Server will not start.
If the syntax is incorrect, open server.properties and edit the catalog.url property to correct the problem. Then restart Essbase Studio Server.
See the topic, “catalog.url” in the Essbase Studio User’s Guide for more information and examples.
Note: The server.properties file is located in. Oracle/Middleware/user_projects/epmsystem1/BPMS/bpms/bin/server.properties.
If you used the “Apply Maintenance Release” option to move from Essbase Studio Release 11.1.2 to this release, you must update the Essbase Studio catalog after installation and configuration. You update the catalog by issuing the reinit command in the Essbase Studio command line client.
For instructions, see the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide, “Updating the Essbase Studio Catalog."
When working with Essbase models based on an Oracle BI EE Business Model data source, Oracle recommends that you enable the “Duplicate member name support” option. Selecting the “Duplicate member name support” option helps resolve member name collisions which are likely to occur in Oracle BI EE Business Model-based Essbase cubes.
(11058371, 11068896)
You can generate a MaxL deploy statement by choosing options in the Cube Deployment Wizard and then saving your selections as a MaxL script.
When redeploying XOLAP cubes, if you then edit the Essbase Studio Server-generated MaxL to remove or change any deployment settings, data may not be consistent.
To redeploy an XOLAP cube, do not change the deployment settings by editing an Essbase Studio Server-generated MaxL script. Instead, Oracle recommends that you launch the Cube Deployment Wizard, make your required selections, then save those selections in a new MaxL script.
(7216055, 9034403)
You can use the MaxL Deploy statement to load members and data into Essbase from a rules file that was created in Essbase Studio. The Deploy statement provides you with the simplest way to accomplish this task.
You may, however, choose to use the MaxL Import Dimensions statement to load members from an Essbase Studio rules file. If you choose to use the Import Dimensions statement to build an outline, note that a problem exists when building an Accounts dimension either from the fact table or from a hierarchy containing only user-defined members. When this is the case, use the following workaround to successfully load the data.
Workaround: Prepare an empty dummy text file that can be called in the MaxL Import Dimensions statement. For example:
import database 'tbc.MaxL1' dimension from local text data_file 'C:\dummy.txt' using server rules_file 'Account' on error append to 'C:\Hyperion\textUn1.log';
(7332195, 8578228)
Two ports are used by Essbase Studio Server to communicate with Essbase Spreadsheet Add-in and Hyperion Smart View. These are transport.port and server.httpPort. Changes to either of these port numbers will affect drill-through operations as described in the following sections.
After initial configuration using the EPM System Configurator, if the transport.port property in the server.properties file is changed manually, the following is the state of drill-through connectivity on cubes built prior to the port adjustment.
·
In Hyperion Smart View, drill-through will not work properly. You
must refresh the port number stored in the cube by following the instructions
in “Updating Cube Linkage.” See the Essbase Studio
User’s Guide.
Note: Cubes built after the port adjustment will
work properly.
· In Essbase Spreadsheet Add-in, drill-through will work properly.
If you add an entry for the server.httpPort property in the server.properties file to change it from the default setting of 9080, the following is the state of drill-through connectivity on cubes built prior to the port adjustment.
·
In Essbase Spreadsheet Add-in, drill-through will not work
properly. In order to use drill-through with Essbase Spreadsheet Add-in on
cubes built prior to the port adjustment, you must redeploy those cubes.
Note: Cubes built after the port adjustment will
work properly.
· In Smart View, drill-through will work properly.
(9460997, 9480016, 10415849)
You may increase the Essbase Studio Console virtual memory setting within the limits specified by your operating system.
For example, on Windows 32-bit platforms, the maximum virtual memory setting is 2048 MB.
Instructions on virtual memory configuration are in “Configuring Virtual Memory” in the Oracle Essbase Studio User’s Guide.
(9492623, 10391499)
The following table summarizes how Essbase Studio Server 11.1.2.1, running in streaming or nonstreaming mode, integrates with Oracle BI EE Server, assuming that Essbase 11.1.2.1.00 is managed by OPMN, and whether streaming or nonstreaming mode is supported for a particular operating system. Also, if further configuration must be completed, there is a reference to the appropriate substep in Step 2; for example, 2a or 2b.
|
Oracle BI EE |
Nonstreaming Mode |
Streaming Mode |
|
11.1.1.3 |
Windows: Supported Modify the essbase.cfg file. See 2b. UNIX and Linux: Not Supported Oracle BI EE ODBC driver has a conflict on common environment variables, such as ORACLE_HOME. |
Windows: Supported UNIX and Linux: Supported See 2c. |
|
10.1.3.4 or later |
Windows: Supported Requires the Oracle BI EE 11.1.1.3 ODBC driver installed on same machine as Essbase Server. See 2a. UNIX and Linux: Supported Manually modify opmn.xml to set the correct environment variables, which are different from 11.1.1.3. See 2d. |
Windows: Supported UNIX and Linux: Supported |
|
10.1.3.3 or earlier |
Windows: Not Supported UNIX and Linux: Not Supported |
Windows: Supported See 2e. UNIX and Linux: Supported See 2e. |
1. On Windows, in nonstreaming mode (server.essbase.streamingCubeBuilding=false in server.properties), Essbase Studio can deploy cubes from Oracle BI EE data sources version 10.1.3.4 or later, as long as the Oracle BI EE ODBC driver is version 11.1.1.3 and resides on the same machine as the Essbase Server.
2.
Complete the steps below, as indicated in the preceding table, depending
on your operating system, Oracle BI EE version, and whether you want to run
Essbase Studio Server in streaming or nonstreaming mode:
a.
Uncomment the ;BPM_ORACLEBI_DriverDescriptor
"Oracle BI Server 11g_OHXXXX" line by removing the semicolon:
BPM_ORACLEBI_DriverDescriptor "Oracle BI
Server 11g_OHXXXX"
b.
Change 11g_OHXXXX to the same
instance number as appears in the Drivers tab of the ODBC Data Source
Administrator; for example:
BPM_ORACLEBI_DriverDescriptor "Oracle BI
Server 11g_OH449923612"
c. On UNIX and Linux, if you are deploying cubes based on Oracle BI EE version 11.1.1.3, you must use streaming mode.
d.
UNIX and Linux, in nonstreaming mode, when deploying cubes based on
Oracle BI EE version 10.1.3.4 data sources, you must add the following
environment variables to the opmn.xml file:
<variable append="true"
id="LD_LIBRARY_PATH"
value="/.../prod1/OracleBI/server/Bin"/><variable
append="true"
id="LD_LIBRARY_PATH"
value="/.../prod1/OracleBI/web/Bin"/>
<variable id="SATEMPDIR" value="/.../prod1/OracleBIData/tmp"/>
<variable id="SAROOTDIR" value="/.../prod1/OracleBI"/>
<variable id="SA_ROOTDIR" value="/.../prod1/OracleBI"/>
<variable id="SADATADIR" value="/.../prod1/OracleBIData"/>
For more information, see “(UNIX) Configuring the Environment for Essbase and
Oracle BI EE Integration” in the Oracle EPM System
Installation and Configuration Guide.
e. On Windows, UNIX, and Linux, cubes may be deployed based on Oracle BI EE version 10.1.3.3 and earlier only if the server.essbase.streamingCubeBuilding property is set to streaming (server.essbase.streamingCubeBuilding=true).
3. ODBC driver configuration for Oracle BI EE running on UNIX is covered in the topic, "(UNIX) Configuring the Environment for Essbase and Oracle BI EE Integration" in the Oracle EPM System Installation and Configuration Guide.
(11073948)
When upgrading from Release 11.1.1.3, during configuration with EPM System Configurator, if the Configure Database task fails for Essbase Studio, review the upgrade log file for a message related to inconsistent object in the catalog, similar to this:
Caused by: com.hyperion.cp.cplutil.scripts.export_import.exceptions.ExportException: Inconsistent object in catalog. Please check the object form : \'Drill Through Reports'\'Supplier', object id : @44#0#101#0@.
Important: Be sure that your 11.1.1.3 release environment is running and available until the Essbase Studio catalog is successfully upgraded.
This error occurs when you rename data source connections which have drill-through reports dependent on them.
If there is an error related to inconsistent objects in drill-through reports, then one or more drill-through reports are invalid and must be corrected before you can upgrade Essbase Studio. Fix inconsistent drill-through reports (drill-through reports that depend on data source connections that have been renamed) by taking any of these actions:
· In the 11.1.1.3 environment, rename the data source connections back to their original names.
· Update the invalid drill-through reports by providing new column values and, optionally, filters, in the Report Contents tab of the drill-through report editor.
or
· Delete the invalid drill-through reports from the 11.1.1.3 environment and then re-create them in the upgraded Essbase Studio environment, if needed.
Then, restart EPM System Configurator and rerun the Configure Database task.
If you are using an Oracle database with Essbase Studio, you may want to configure the associated Oracle JDBC drivers with Oracle Advanced Security. Click the following link for information on Oracle Advanced Security:
http://download.oracle.com/docs/cd/B19306_01/network.102/b14268/asojbdc.htm#i1006717
The most recent version of each EPM System product guide is available for download from the Enterprise Performance Management System Documentation area of the OTN Web site (http://www.oracle.com/technology/documentation/epm.html). For faster access to the documentation, you can also use the Enterprise Performance Management Documentation Portal (http://www.oracle.com/us/solutions/ent-performance-bi/technical-information-147174.html) which also links to EPM Supported Platform Matrices, My Oracle Support, and other information resources.
Deployment-related documentation is also available from the Oracle E-Delivery Web site (http://edelivery.oracle.com/EPD/WelcomePage/get_form).
Individual product guides are available for download on the Oracle Technology Network Web site only.
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.
The following items were not documented in the Accessibility appendix of the Essbase Studio User’s Guide (PDF and HTML help formats):
|
Element Name |
Equivalent |
|
Name |
Alt+N |
|
Type |
Alt+T |
|
Look In |
Alt+L |
|
Browse |
Alt+B |
|
Search |
Alt+S |
|
Clear |
Alt+C |
After clicking Search or pressing Alt+S, if there are search results returned, press Tab to move focus to the Search Result portion of the Search tab, and navigate the search results. If there are no search results, you may not tab to the Search Results portion of the tab and this message appears: No elements found in search.
Refer to Table 7, "Accessing Elements in the Metadata Navigator and Source Navigator," in "Appendix A, Accessibility" in the Oracle Essbase Studio User's Guide, which contains instructions for navigating within a tree structure.
|
Element Name |
Equivalent |
|
Changed Tables |
Alt+T |
|
Changed Columns |
Alt+C |
|
Dependent Dimension Elements and Joins |
Alt+D |
|
Save Dependencies List as File |
Alt+F |
|
Refresh |
Alt+R |
|
Element Name |
Equivalent |
|
Table Status (Errors and Warnings) |
Alt+T |
|
Select All Tables |
Alt+A |
|
Dependent Dimension Elements and Joins |
Alt+E |
|
Save Dependencies List as File |
Alt+S |
|
Delete |
Alt+D |
|
Element Name |
Equivalent |
|
Login |
Alt+L |
This shortcut key is added to the Essbase Login dialog box which is accessed when creating an Essbase Server connection in the Cube Deployment Wizard.
|
Element Name |
Equivalent |
|
Data Encryption |
Alt+E |
Note that the following preview options are not available for measure hierarchies.
|
Element Name |
Equivalent |
|
Preview With Caption Binding |
Alt+P+C |
|
Preview With Key Binding |
Alt+P+K |
|
Element Name |
Equivalent |
|
Save Minischema |
Shift+F10, then S |
|
Add to Metadata Navigator |
Shift+F10, then M |
View tabs are the tabs for Metadata Navigator, Search, Data Sources, Minischemas, and Console Messages.
|
Action |
Key or Key Combinations |
|
Close a view tab |
Shift-Tab until focus is on the actual tab title. · Shift-Tab twice for Metadata Navigator, Data Sources, and Minischemas tabs · Shift-Tab once for Search and Console Messages tabs Then, Alt+- (hyphen), use down arrow to select Close (or press C) |
The Browse command and the Alt+B shortcut has been removed.
(10383674, 10647506)
The topic, "Upgrading the Essbase Studio Catalog and Data" has been updated. Please disregard the topic in the Oracle Essbase Studio User's Guide and refer to the topic below.
To move Essbase Studio from release 11.1.1.3 to the 11.1.2.1 release, you perform an upgrade. To move from release 11.1.2 to 11.1.2.1, you apply the maintenance release.
The upgrade or maintenance release procedure for Essbase Studio is part of the configuration process for EPM System. See the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide for more information. Complete the tasks applicable to your environment in the order noted in the guide.
After configuration, perform these tasks in Essbase Studio:
1. If Essbase Server has moved, perform the rehosting procedure so that Essbase connections point to the new server location, as described in "Updating References to Rehosted EPM System Products" in the Oracle Essbase Studio User's Guide.
2. If Essbase Studio Server has moved, for deployed applications that reference the old server location, update the cube linkage, as described in "Updating Cube Linkage" in the Oracle Essbase Studio User's Guide.
3. For text file data sources:
o Specify either the location from an earlier release, or the replicated location for the Essbase Studio data files by modifying the default EPM_ORACLE_INSTANCE/BPMS/bpms1/datafiles location provided in the EPM System Configurator. See the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide for more information.
o Edit the connection properties for any text file connections to point to the new location of the text files, as described in "Editing Data Source Connection Properties" in the Oracle Essbase Studio User's Guide.
o After configuration, if you move your text files to another location, edit the server.datafile.dir property in the server.properties file and edit the connection properties for any text file connections to point to the new location of the text files. See "server.datafile.dir" and "Editing Data Source Connection Properties" respectively in the Oracle Essbase Studio User's Guide.
4. If Performance Management Architect Dimension Server has moved, edit the connection properties for any Performance Management Architect Dimension Server connections that point to the old server location, as described in "Editing Data Source Connection Properties" in the Oracle Essbase Studio User's Guide.
(11724835)
Revisit this in PS2 to see whether we keep this role, then add or not to the Studio UG and update the Security Guide.The Essbase Studio user role, cpDMDSAdmin, was previously undocumented. This role has all the privileges of the Essbase Studio Viewer, cpDSAdmin, and cpDM roles. To assign this role, select both the cpDSAdmin and cpDM roles when provisioning.
For information on provisioning and on all Essbase Studio roles, see the Oracle EPM System User and Role Security Guide.
To perform an export/import of the Essbase Studio catalog database, you must be provisioned as Administrator (cpAdmin role) in Hyperion Shared Services.
For information on provisioning and on all Essbase Studio roles, see the Oracle EPM System User and Role Security Guide.
The following rules for drill-through template SQL were not previously documented:
· All pairs of predefined variables that are associated with dimension intersection values and dimension table columns must be included in the user-defined SQL. For example, the intersection of the dimension Product is specified by the following expression in the standard SQL template:
$$Product-COLUMN$$ IN ($$Product-VALUE$$)
This expression must also be included in the user-defined SQL template.
· In the user-defined SQL template, users should reuse the same alias names that were generated by the Essbase Studio Server in the predefined SQL template.
It is our goal to make Oracle products, services, and supporting documentation accessible to the disabled community. Oracle Essbase Studio supports accessibility features, which are described in Appendix A in the Oracle Essbase Studio User's Guide. The most up-to-date version of this guide can be found in the EPM 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.
Copyright © 2011, Oracle and / or its affiliates. All rights
reserved.
http://www.oracle.com