Table of Contents:
This document includes important, late-breaking information about this release of Oracle Essbase Studio. Review this Readme thoroughly before installing Essbase Studio.
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.
14255474 - Data values may be truncated after the decimal point when they are loaded into Oracle Essbase. For example, 1.333 in the data source may be loaded into Essbase as 1.
14102171 - In Essbase outlines built using Essbase Studio, aliases are not being applied to non-level-zero (non-leaf) attribute members.
14092254 - On aggregate storage databases, when using the MaxL deploy statement to create hierarchies (outside of Accounts) with user-defined members at the top level and dimension elements for the subsequent levels, the MaxL Shell returns an error.
14033904 - Joins are in the wrong direction, from primary key to foreign key. The correct direction is from foreign key to primary key.
For Essbase Studio Console to support bi-directional languages, such as Hebrew and Arabic, you must modify startStudio.bat to include the “-dir rtl” parameter after start EssbaseStudio.exe.
Modify startStudio.bat under <Middleware_HOME>
Add the parameter "-dir rtl" after “start EssbaseStudio.exe.”
@echo OFF set JAVA_HOME="C:\Program Files (x86)\Java\jre6" SET PATH=%JAVA_HOME%\bin;%PATH%; start EssbaseStudio.exe –dir rtl exit
Save the file.
Run this file to start Essbase Studio Console.
16366858--Unable to load members with non-English characters to an Essbase Unicode outline with a Teradata data source.
15885976--When you import an Essbase Studio catalog XML file with the option to “Check for elements and overwrite them” selected, and the XML file you are importing contains a data source connection that also exists in the target catalog, then minischemas and other objects such as tables, views, and synonyms will not be imported.
Workaround: If there are differences between the exported and existing data source, complete the following tasks:
Right-click on the data source connection and select Incremental Update. In the Incremental Update dialog box, select tables, views, and synonyms to add to the data source connection.
Right-click on individual tables, views, and synonyms in the data source connection and select Refresh to add or remove columns and update properties.
14629926--If you start Essbase Studio Server on a machine that is different from the machine where you ran the cube deployment, drill-through reports will not work as expected.
Workaround: Manually update the Essbase Studio Server information from the Essbase Studio Console:
Go to Tools, then Update Cube Linkage.
Update the information in the Cube Linkage Essbase Studio Server column to reflect the correct Essbase Studio Server.
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 -- If 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.
16493006--Because Essbase Studio does not support RAC database as a catalog, Essbase Studio cannot be launched successfully after BI Installation if, during installation, you specify a RAC database connection string with multiple nodes. For example: host1:port1:sid1^host1:port1:sid1@sid.
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 Business Intelligence Enterprise Edition data source.
7366645 -- When using Oracle Hyperion Smart View for Office or 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 Oracle Essbase Integration Services.
7665495 -- 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
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 -- 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 -- When migrating an OLAP metaoutline from 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 Oracle Essbase 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 -- Microsoft Windows authentication is not supported for data source connections to Microsoft SQL Server.
9315569 -- 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 “Setting Up a History Table for Varying Attributes” in the Oracle Essbase Studio User's Guide.
9326364 -- 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, "VARYPER," 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 -- When deploying cubes in nonstreaming mode (the Enable streaming mode for cube deployment check box is cleared), deployment fails when the Essbase model is based on a Unicode data source.
Use streaming mode: In the Cube Deployment Wizard, ensure that the Enable streaming mode for cube deployment check box is selected.
Use nonstreaming mode with the data source enabled for N-CHAR support:
First, create a DSN and enable the N-CHAR support option as follows:
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.
On UNIX or Linux, edit the odbc.ini file to create a new DSN, and set the EnableNcharSupport value as follows:
Then, the Cube Deployment Wizard, complete these steps:
In the Essbase Server connection options page, select the ODBC (Enter ODBC DSN Name) option and provide the DSN you created.
In the Cube deployment options page, ensure that the Enable streaming mode for cube deployment check box is cleared.
See the Cube Deployment chapter in the Oracle Essbase Studio User's Guide for information on using the Enable streaming mode for cube deployment check box.
9433391 -- 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.
Essbase Studio Server uses the nonstreaming cube building method automatically for text file data sources; you will not be asked about or notified of this internal load method.
Cube deployment progress statistics are not supported on text file data sources.
9477466 -- In Smart View, when performing drill-through from an Essbase Studio-sourced cube to Oracle Hyperion Financial Data Quality Management, if the Oracle Enterprise Performance Management System Single Sign-On token expires before the sessions of all products involved expire (Workspace, Oracle Hyperion Provider Services, Essbase, Essbase Studio, Oracle Hyperion Financial Data Quality Management), 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.
9492526, 9502269-- On Windows, when Essbase is started using OPMN, cube deployment fails for cubes built from Oracle BI EE 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 Oracle Essbase Studio User's Guide for more information.
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 Oracle Essbase Studio User's Guide for information on this property.
9561925 -- 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 cp_server_key table in the Essbase Studio catalog database.
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 -- Cubes 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 -- The day attributes of a calendar hierarchy are not all listed under the hierarchy in the Essbase Model Properties dialog. (Related to bug 11663358.)
13810033 -- Essbase Studio does not support IPv6 protocol on Microsoft Windows platforms. Essbase Studio supports IPv6 protocol only on UNIX platforms.
14155099, 14462547 -- Netezza Data Source for Essbase Studio. Unable to connect to a Netezza data source using non-streaming mode in Essbase Studio.
Workaround: In non-streaming mode, the connection to a data source is made by Essbase, not Essbase Studio. Data source drivers are specified in the Essbase configuration file (essbase.cfg). By default, some data source drivers are disabled by the presence of a semicolon (;) comment indicator at the beginning of the data source entry. In the following example, the Netezza driver is disabled.
BPM_Oracle_DriverDescriptor "DataDirect 6.1 Oracle Wire Protocol" BPM_DB2_DriverDescriptor "DataDirect 6.1 DB2 Wire Protocol" BPM_SQLServer_DriverDescriptor "DataDirect 6.1 SQL Server Native Wire Protocol" ;BPM_SQLServer_DriverDescriptor "SQL Server" ;BPM_Netezza_DriverDescriptor "NetezzaSQL" BPM_Teradata_DriverDescriptor "Teradata" ;BPM_ORACLEBI_DriverDescriptor "Oracle BI Server 11g_OHXXXX" ;BPM_ORACLEBI_DriverDescriptor "Oracle BI Server" BPM_MySQL_DriverDescriptor "DataDirect 6.1 MySQL Wire Protocol
Edit essbase.cfg to make sure that the data sources you are using are listed and are not disabled by the semicolon comment indicator.
The Netezza ODBC driver must be installed on the machine on which Essbase Server runs.
The Oracle 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 Working with the Virtual Memory Setting 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 Oracle Essbase Studio User's Guidefor more information and examples.
The server.properties file is located in. Oracle\Middleware\instances\instance1\EssbaseStudio\essbasestudio1\bin.
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.
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.
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-generated 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';
Two port properties are used by Essbase Studio Server to communicate with Spreadsheet Add-in and Smart View. These are transport.port and server.httpPort. Changes to the port numbers specified in these properties will affect drill-through operations as described in the following sections.
After initial configuration using the Oracle Hyperion Enterprise Performance Management 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 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 Oracle Essbase Studio User's Guide.
Cubes built after the port adjustment will work properly.
In 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 Spreadsheet Add-in, drill-through will not work properly. In order to use drill-through with Oracle Essbase Spreadsheet Add-in on cubes built prior to the port adjustment, you must redeploy those cubes.
Cubes built after the port adjustment will work properly.
In Oracle Hyperion Smart View for Office, drill-through will work properly.
(9460997, 9480016, 10415849)
On the machine where Essbase Studio Console is running, you may increase the 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.
Table 1 summarizes how Essbase Studio Server, running in streaming or nonstreaming mode, integrates with Oracle BI EE Server, assuming that Essbase 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, step 2.a or step 2.b.
Table 1. Essbase Studio Server Integration with Oracle BI EE Server
Oracle BI EE Version
Nonstreaming Mode server.essbase.streamingCubeBuilding=false
Streaming Mode server.essbase.streamingCubeBuilding=true
Modify the essbase.cfg file. See step 2.b.
UNIX and Linux: Not Supported
Oracle BI EE ODBC driver has a conflict on common environment variables, such as ORACLE_HOME.
UNIX and Linux: Supported
See step 2.c.
10.1.3.4 or later
Requires the Oracle BI EE 220.127.116.11 ODBC driver installed on same machine as Essbase Server. See step 2.a.
UNIX and Linux: Supported
Manually modify opmn.xml to set the correct environment variables, which are different from 18.104.22.168. See step 2.d.
UNIX and Linux: Supported
10.1.3.3. or earlier
Windows: Not Supported
UNIX and Linux: Not Supported
See step 2.e.
UNIX and Linux: Supported
See step 2.e.
To complete any further configuration required by Table 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 22.214.171.124 and resides on the same machine as the Essbase Server.
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:
BPM_ORACLEBI_DriverDescriptor "Oracle BI Server 11g_OHXXXX"
BPM_ORACLEBI_DriverDescriptor "Oracle BI Server 11g_OH449923612"
<variable append="true" id="LD_LIBRARY_PATH" value="/.../prod1/OracleBI/server/Bin"/>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 Enterprise Performance Management System Installation and Configuration Guide.
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).
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 Enterprise Performance Management System Installation and Configuration Guide.
When Essbase Studio Server is installed and configured as a Windows service, you cannot start it as a service using Windows authentication. In order configure Essbase Studio Server to take advantage of Windows authentication, you must do the following:
If already running, stop the Essbase Studio Server service.
Edit the catalog.username property in the Essbase Studio server.properties file as follows:
Do not add any user name or other text to the catalog.username property.
Start Essbase Studio Server using either the Start menu or the start_BPMS_bpms<instance>_Server.bat file.
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:
For user-defined SQL queries from Essbase Studio, the data source administrator must ensure that data source users only have permissions to read the data of the tables that they require, and no more. This will prevent users from potentially running queries that access data to which they are not entitled.
When you import an Essbase Studio catalog XML file with the option to Check for elements and overwrite them selected, and the XML file contains a data source connection that also exists in the target catalog, then minischemas and other objects such as tables, views, and synonyms will not be imported. Workaround: delete the data source connection in the target catalog before importing the XML file.
To configure Teradata as a data source:
Essbase Studio uses JDBC drivers. The JDBC Teradata driver must be installed on the computer on which Essbase Studio Server runs.
Essbase Studio uses the JDBC Teradata driver to deploy cubes in streaming mode.
To deploy cubes in non-streaming mode, the ODBC Teradata driver must be installed on the computer on which Essbase Server runs.
Essbase uses ODBC drivers. The ODBC Teradata driver must be installed on the computer on which Essbase Server runs.
<variable id="ESS_CSS_JVM_OPTION7" value="-Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration"/>
<variable append="true" id="PATH" value="C:\Program Files\Teradata\Client\14.00\Shared ICU Libraries for Teradata\lib"/>
When using Teradata data sources with Essbase, and using OPMN to monitor and control the Essbase Agent process, you must update the opmn.xml file with variables for the operating system you are using.
The absolute path value cannot contain spaces. The examples of absolute path values are based on a 64-bit machine configuration.
Add these variables:
TWB_ROOT: Teradata root
PATH: Teradata shared libraries
PATH: Teradata client DLL libraries
PATH: Teradata Call-Level Interface Version 2 routines
PATH: Teradata message DLL libraries
64-bit Windows example:
<variable id="TWB_ROOT" value="C:\PROGRA~1\Teradata\Client\14.00"/> <variable append="true" id="PATH" value="C:\PROGRA~1\Teradata\Client\14.00\SHARED~1\lib"/> <variable append="true" id="PATH" value="C:\PROGRA~1\Teradata\Client\14.00\TERADA~1\bin64"/> <variable append="true" id="PATH" value="C:\PROGRA~1\Teradata\Client\14.00\CLIv2"/> <variable append="true" id="PATH" value="C:\PROGRA~1\Teradata\Client\14.00\TERADA~1\msg64"/>
Add these variables:
LIBPATH: Teradata ODBC libraries
LIBPATH: Teradata shared libraries
LIBPATH: ODBC components needed to load Teradata ODBC drivers
LIBPATH: Teradata client libraries
COPERR: Directory where the errmsg.txt file resides
NLSPATH: Teradata message libraries
64-bit AIX example:
<variable append="true" id="LIBPATH" value="/opt/teradata/client/ODBC_64/lib"/> <variable append="true" id="LIBPATH" value="/opt/teradata/client/13.10/tdicu/lib64"/> <variable append="true" id="LIBPATH" value="/usr/odbc/lib:/usr/odbc/drivers"/> <variable append="true" id="LIBPATH" value="/usr/lib:/usr/teragss/aix-power/client/lib"/> <variable id=" COPERR" value="/usr/libperion/essbase"/> <variable id="NLSPATH" value="/opt/teradata/client/13.10/odbc_32/msg/%N"/> <variable append="true" id="NLSPATH" value="/usr/lib/nls/msg/%L/%N"/> <variable append="true" id="NLSPATH" value="/usr/lib/nls/msg/%L/%N.cat"/>
Add these variables:
TWB_ROOT: Teradata root
TD_ICU_DATA: Teradata shared libraries
NLSPATH: Teradata ODBC message libraries
COPERR: Directory where the errmsg.txt file resides
COPLIB: Directory where the libcliv2.so library file resides
LD_LIBRARY_PATH: Teradata libraries
PATH: Teradata client directories
The errmsg.txt and libcliv2.so files typically reside in the same directory. Therefore, the value for the COPERR and COPLIB variables is typically identical.
64-bit LINUX example:
<variable id="TWB_ROOT" value="/opt/teradata/client/13.10/tbuild"/> <variable id="TD_ICU_DATA" value="</opt/teradata/client/13.10/tdicu/lib64> "/> <variable id="NLSPATH" value="</opt/teradata/client/13.10/odbc_64/msg/%N > "/> <variable append=true id=NLSPATH value=/opt/teradata/client/13.10/tbuild/msg64/%N/> <variable id="COPERR" value="/usr/lib64"/> <variable id="COPLIB" value="/usr/lib64"/> <variable append=true id=LD_LIBRARY_PATH value=/opt/teradata/client/13.10/tbuild/lib64/> <variable append=true id=LD_LIBRARY_PATH value=/usr/lib64/> <variable append=true id=PATH value=/opt/teradata/client/13.10/tbuild/bin/> <variable append=true id=PATH value=/opt/teradata/client/13.10/tbuild/lib64/>
Essbase: Use the Data Prep Editor in Administration Services Console to connect to a Teradata database using a DNS.
Essbase Studio: Perform a cube deployment in non-streaming mode, which uses the Teradata ODBC driver.
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.
To perform an export/import of the Essbase Studio catalog database, you must be provisioned as Administrator in Oracle Hyperion Shared Services. For information on provisioning and on all Essbase Studio roles, see the Oracle Essbase Studio User's 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.
In the “Limitations and Guidelines” appendix, under “General Limitations” in the “Cube Deployment Limitations and Guidelines” section, the statement, “Incremental builds for XOLAP-enabled models are not supported. ” is incorrect. You can ignore this statement. Starting with Release 126.96.36.199.102, Essbase Studio supports incremental builds for XOLAP-enabled models.
When dimension elements have sort orders applied to them and, in the Essbase model, the members based on those dimension elements have prefix or suffix transformations applied to them, these members will not sort correctly after the model is deployed.
Workaround: If you require prefix or suffix transformations on a member that has sort orders applied to the underlying dimension element, you can edit the key binding expression for the element to add the transformation. Do not use the transformation functionality in the Essbase model in this case.
For example, using the TBC database, a Product dimension is built using the following hierarchy:
FAMILY |_ SKU
Before applying the transformation to the key binding expression, the dimension element properties are set as follows:
Dimension element FAMILY—with Key and Caption Bindings set to PRODUCTDIM.FAMILY, and Sort Column set to PRODUCTDIM.FAMILY
Dimension element SKU—with Key and Caption Bindings set to PRODUCTDIM.SKU, and Sort Column set to PRODUCTDIM.SKU
Now edit the key binding expression using concatenation to add a prefix or suffix.
For example, to add SKU from the PRODUCTDIM table as a suffix to the FAMILY dimension element, the additional text in bold below is added to the key binding expression:
connection : \'TBC-oracle'::'TBC.PRODUCTDIM'.'FAMILY' || "_" || connection : \'TBC-oracle'::'TBC.PRODUCTDIM'.'SKU'
In a multichain hierarchy containing a base chain and attribute chains, when removing the base chain, the Essbase model resync operation will succeed, but cube deployment of this model will fail.
Note that the Essbase model resync operation does not validate the model. If the resynced model contains errors, you will not be notified. Therefore, you must validate the model separately by opening it in the Essbase Model Properties dialog box and performing the steps in the “Validating Model Properties” topic in the Oracle Essbase Studio User's Guide.
In a multichain hierarchy containing a base chain and an attribute chain, if an intermediate level in an attribute chain is added or deleted and then model resync is performed, the attribute settings are removed from attribute dimension.
Whenever you add or remove levels in an attribute chain, you should perform the model resync, and then review and reset any attribute or varying attribute properties in the affected Essbase models. Also, Oracle recommends that you validate the model before attempting cube deployment.
If you remove the leaf level of a hierarchy that is included in a varying attribute, and then perform a model resync, the resync will appear to be successful but the varying attribute will no longer work. Deployment of a cube that uses this hierarchy will fail.
As stated in the previous item (13005538), after performing the model resync, review and, where necessary, reset attribute or varying attribute properties in affected Essbase models. Also, be sure to validate models before attempting cube deployment.
In the topic, “About Model Resync,” there are two erroneous items in the list of operations that trigger the need for a model resync. Those operations are:
Renaming the schema
Renaming the hierarchy
Note that renaming a cube schema or a hierarchy does not trigger the need for a model resync.
When previewing drill-through reports in Essbase Studio, the maximum number of rows returned is 1024.
Note: You preview, or test, drill-through reports by clicking the Test button in the Report Contents tab of the drill-through report editor.
When working with an Essbase model that is based on an Oracle BI EE data source using the Business Model option, and you selected the Create cube schema and Essbase model option when creating the data source connection, then the ASO storage model option and Duplicate member name support option are enabled by default. You may clear either or both of these options if you require.
Oracle recommends, however, 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 Business Intelligence Enterprise Edition Business Model-based Oracle Essbase cubes
In the General tab for members in the Essbase Model Properties dialog box, the former “Comments” drop-down list box (which also accepted hand-typed comments) has been converted to a new Comments group with these options:
Comments—a text box where you enter a comment for the member.
From External Source—a drop-down list box where you select an applicable database column that contains comments, which are loaded along with members during cube deployment.
You can select one of the above options per member.
It is our goal to make Oracle products, services, and supporting documentation accessible to the disabled community. Oracle's Oracle Essbase Studio supports accessibility features, which are described in the Oracle Essbase Studio Accessibility Guide. The most up-to-date version of this guide can be found 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.