ORACLE® ESSBASE STUDIO

Release 11.1.2.3.000

Readme

CONTENTS IN BRIEF

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

New Features in this Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Server Properties Configuration Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Installation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Supported Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Supported Paths to this Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Defects Fixed in this Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Tips and Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Documentation Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

PurposeThis document includes important, late-breaking information about this release of OracleEssbase Studio. Review this Readme thoroughly before installing Essbase Studio.

New Features in this ReleaseFor new features relating to installation, architecture, and deployment changes in this release,see “New Features in this Release” in the Oracle Enterprise Performance Management SystemReadme.

If you are coming from Release 11.1.2.0, 11.1.2.1, or 11.1.2.2, use the Cumulative FeatureOverview tool to review the list of new features added between those releases. This tool enablesyou to identify your current products, your current release version, and your targetimplementation release version. With a single click, the tool quickly produces a customized setof high-level descriptions of the product features developed between your current and targetreleases. This tool is available here:

https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1092114.1

Server Properties Configuration UpdateStarting in Release 11.1.2.3, the following Essbase Studio server properties are stored in theOracle Hyperion Shared Services Registry database:

l server.css.URL

l catalog.url

l catalog.password

l server.httpPort

l catalog.username

l catalog.db

l transport.port

l server.hss.bpmApplication

l server.datafile.dir

The 11.1.2.3 Oracle Essbase Studio User's Guide describes all server properties as being in theserver.properties file. To view or modify the settings in Shared Services Registry, use theepmsys_registry utility, described in the Oracle Enterprise Performance Management SystemDeployment Options Guide.

Alternatively, you can create a server.properties file and enter updated settings there, sincethe settings in server.properties override the settings stored in the Shared Services Registry.

The following server properties can be added in the server.properties file and are not setin the Shared Services Registry:

2

l server.timeoutPeriod

l server.queueSize

l server.threadCount

l server.sql.fetchSize

l server.tempDir

l server.charset

l server.readLockTimeOut

l server.writeLockTimeOut

l server.essbase.TPTapi

l server.essbase.disableDistinct

l server.runInBackground

l server.essbase.blindShare

l oracle.jdbc.ReadTimeout

l data-source-type.pool.maxsize

l data-source-type.cache.size

l server.essbase.uniqueMemberFromCaptionBinding

l catalog.pool.size

l server.jdbc.teradata.properties

l server.query.skipValidation

Note: Before you can add server properties to server.properties, you must create the file.Using a text editor, create a new file in EPM_ORACLE_ INSTANCE/BPMS/bpms/bin andname it server.properties.

Installation InformationLate-breaking information about the installation of Oracle Enterprise PerformanceManagement System products is provided in the Oracle Enterprise Performance ManagementSystem Installation and Configuration Readme. Review this information thoroughly beforeinstalling EPM System products.

Supported PlatformsInformation about system requirements and supported platforms for EPM System products isavailable in spreadsheet format in the Oracle Enterprise Performance Management SystemCertification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported SystemConfigurations page on Oracle Technology Network (OTN):

3

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

Supported LanguagesInformation about supported languages for EPM System products is available in spreadsheetformat on the Translation Support tab in the Oracle Enterprise Performance Management SystemCertification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported SystemConfigurations page on OTN:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

Supported Paths to this ReleaseYou can upgrade to EPM System Release 11.1.2.3 from the following releases:

Note: For upgrading instructions, see the Oracle Enterprise Performance Management SystemInstallation and Configuration Guide, “Upgrading EPM System Products.”

Table 1 Supported Paths to this Release

Upgrade Path From Release ... To Release 11.1.2.3

11.1.2.x Apply the maintenance release to Release 11.1.2.3.

For Oracle Hyperion Financial Close Management, applying the maintenancerelease is supported only from Release 11.1.2.1 and 11.1.2.2.

11.1.1.4.x Upgrade to Release 11.1.2.3.

Release 11.1.1.0.x to 11.1.1.3.x Apply the maintenance release to Release 11.1.1.4 and then upgrade to Release11.1.2.3.

An environment that includes multiple releases,which can include an environment with one instanceof Oracle Hyperion Shared Services or an environmentwith two instances of Shared Services

See "Upgrading from an Environment with Multiple Releases" in the "UpgradingEPM System Products" chapter in the Oracle Enterprise Performance ManagementSystem Installation and Configuration Guide.

Defects Fixed in this ReleaseThis section includes defects fixed in Release 11.1.2.3.000. To review the list of defects fixedbetween earlier releases, use the Defects Fixed Finder This tool enables you to identify theproducts you own and your current implementation release. With a single click, the tool quicklyproduces a customized report of fixed-defect descriptions with their associated platforms andpatch numbers. This tool is available here:

https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1292603.1

l 14795937 -- For dimensions tagged as Accounts, solve order is not applied during cube build.After setting the non-zero value applying the changes, the new value is not saved. If you close

4

and re-open the Model Properties Wizard, you will see that the value is reset to zero (thedefault).

l 16100032--On Windows XP, sort order does not work as expected in the Italian version ofEssbase Studio Console. When viewing the properties of a Dimension Element in MetadataNavigator, you can select sort order, but when you leave and come back, the word"Ascending" is displayed instead of the Italian "Crescente." Also, once Crescente orDescrescente (Ascending or Descending) is selected and saved, when you go back intosettings, the sort order is changed back to the English "Ascending", regardless of what wasselected in Italian.

l 15955288--On aggregate storage databases, when using the MaxL deploy statement to createhierarchies (outside of Accounts) with user-defined members at the top level and dimensionelements for the subsequent levels, the MaxL Shell fails to respond.

l 14180646 -- Essbase Studio loads the Oracle Database value "NULL" as 0, when it shouldload null values as #MISSING.

l 14311212 - Upgrading Essbase Studio catalog to newer version fails when a metadatadescription field contains a string enclosed by double-quotes.

Known IssuesThe following are the noteworthy known issues of this release.

l 16921268--Unable to shutdown Essbase Studio Server if installed on a custom port. Theworkaround is to modify stopServer.sh by adding Dserver.url="localhost:<newport num>". For example, modify this entry:

"${JAVA_HOME}/bin/java" -Xms128m -Xmx768m $JAVA_OPTIONS -cp "${EPM_ORACLE_HOME}/products/Essbase/EssbaseStudio/Server/server.jar" com.hyperion.cp.api.ShutdownRequest

To this:

"${JAVA_HOME}/bin/java" -Xms128m -Xmx768m -Dserver.url="localhost:<new port num>" $JAVA_OPTIONS -cp "${EPM_ORACLE_HOME}/products/Essbase/EssbaseStudio/Server/server.jar" com.hyperion.cp.api.ShutdownRequest

l 16298982--When Oracle Essbase is running on Japanese Linux, loading Japanese charactersto the outline in a native Japanese application does not work in non-streaming mode.Workaround: Use streaming mode instead.

l 16423924--The Week element is missing from the Create date elements dialog box. Theavailable options are Year, Quarter, Month, and Day of week. Workaround: Create adimension element manually, using this syntax in the Caption Binding and Key Bindingfields. Be sure to select Advanced for Key Binding.

To represent the week of the month:

'WM'( connection : \'tbc'::'TBC.SALES'.'TRANSDATE' ) . toString 'WM'( connection : \'tbc'::'TBC.SALES'.'TRANSDATE' )

5

To represent the week of the year:

'WY'( connection : \'tbc'::'TBC.SALES'.'TRANSDATE' ) . toString'WY'( connection : \'tbc'::'TBC.SALES'.'TRANSDATE' )

For more information, see Creating an Expression on Which to Base a Dimension Elementin the Oracle Essbase Studio User's Guide.

l 16435266--In cases with parent/child columns, creating more than one self join using asingle text file fails.

l 16517700--If server.query.skipValidation=true is set in server.properties,validation for User-defined SQL in Drill-through reports does not work correctly. Validationof an invalid user-defined SQL statement incorrectly returns "User-defined SQL is valid."

l 16522882--After upgrading from 11.1.2.2.000 to 11.1.2.3.000, adding a database source orissuing a reinit command may result in a JDBC driver error message. Workaround: RestartEssbase Studio Server if you get the JDBC Driver error message.

l 16292007--When Oracle RAC is the data source, cube deployment in non-streaming modewith ODBC connection string is not supported.

l 14625545 -- When dimension elements are created using delayed key bindings, and thoseelements are then used in an Essbase model that is enabled for duplicate member namesupport, cube deployment fails. Workaround: In the dimension elements, use the Advancedoption and edit the Key Binding manually. For example, using the TBC database, for adimension element created from the UDAMKTSIZE column, the Delayed key binding thatautomatically appears in the hierarchy is:

class : \'tbc'\'REGION'\'REGION'.'caption' || "_" || class : \'tbc'\'MARKET'\'UDAMKTSIZE'.'caption' Instead, edit the key binding in the dimension element by using the Advanced option as follows: connection : \'tbc'::'TBC.REGION'.'REGION'||connection : \'tbc'::'TBC.MARKET'.'UDAMKTSIZE'

l N/A -- Integration Services catalog migration is not supported on 64-bit UNIX platformsor on the Windows 2008 64-bit platform.

l N/A -- Oracle Essbase Spreadsheet Add-in for Excel works in native locale. If SpreadsheetAdd-in does not receive data in native locale, drill-through on cubes built in Essbase Studiois not supported.

l N/A -- Transformation rules defined in the Essbase model will not be used in querygeneration for drill-through operations.

Workaround: You may edit the expressions for the dimension element's caption binding totransform members.

l N/A -- If Oracle is your catalog database: Essbase Studio no longer issues the ALTERSYSTEM command when connecting to the catalog database. For increased performance,add the ALTER SYSTEM statement to the Oracle database user's privileges for the EssbaseStudio catalog user.

Following are the recommended settings:

6

ALTER SYSTEM SET open_cursors=300 SCOPE=MEMORY

The catalog user is specified in the Shared Services Registry during configuration and shouldhave the privileges necessary to execute the ALTER SYSTEM statement.

l 7665495 -- A 255-character limit applies to certain objects that you name in Essbase Studio.These objects are:

m Data source connection names

m User-defined table names

m Metadata element names, such as dimension elements and hierarchies

m Alias sets

m Cube schema names

m Drill-through report names

These are the limits on Essbase application and database names:

m 8 bytes for non-Unicode

m 30 characters for Unicode

l 6576813 -- The JISX0213 Japanese character set, which replaces the JISX0208 and JISX0212Japanese character sets, is supported on Windows Vista. The Essbase family of products doesnot support the JISX0213 Japanese character set.

l 7138321 -- You cannot deploy an XOLAP-enabled Essbase model that is based on an OracleBusiness Intelligence Enterprise Edition data source.

l 7366645 -- When using Oracle Smart View for Office or Oracle Essbase Spreadsheet Add-in to query cubes built in Essbase Studio, if the intersection for a drill-through cell isrepresented by both a base member and one or more associated attribute members, youcannot perform drill-through on that cell.

Specifically, drill-through will not work on an intersection (cell) that is represented bymembers of a base dimension and members of attribute dimensions.

When specifying intersections for a drill-through report in Essbase Studio, do not specifyboth the base and attribute hierarchies from a multichain hierarchy. Select only one of thehierarchies for drill-through.

If you require drill-through from an intersection containing a base member and attributemembers, you must build the cube using Oracle Essbase Integration Services.

l 8661977 -- When deploying a cube for the first time, and the cube contains text or datemeasures, the data is loaded correctly. Upon subsequent deployments of the cube, selectingthe "Load data" option along with either the "Add to existing data" or "Subtract from existingdata" 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.

l 8897922 -- When migrating an OLAP metaoutline from Integration Services to EssbaseStudio, members in a hierarchy may not be sorted properly in the deployed Essbase cube ifboth transformation and sorting rules are defined on the original Oracle Essbase Integration

7

Services member set. In Essbase Studio, performing transformation in Essbase ModelProperties does not resolve the issue.

Workaround: Perform transformation in the Dimension Element Properties dialog box byediting the key binding expression of the dimension elements.

l 8908738, 7127257 -- Microsoft Windows authentication is not supported for data sourceconnections to Microsoft SQL Server.

l 9315569 -- The labeling rules listed in the Editing Labeling Rules dialog box were nottranslated and appear in English for all languages.

The Editing Labeling Rules dialog box is accessed from the Time Depth area of the CalendarHierarchy dialog box, as described in "Defining Time Depth" in the Oracle Essbase StudioUser's Guide.

l 9325297 -- Varying attributes do not support NULL values in the "FROM" or "TO" columnsof the "history" table. When working with varying attributes, if the history table containsrows with a NULL value in either the FROM or TO columns, then the attribute values fromthese rows are not built into an attribute dimension.

Workaround: Ensure that there are non-NULL values in the FROM and TO columns of thehistory table. For more information on history tables, see “Setting Up a History Table forVarying Attributes” in the Oracle Essbase Studio User's Guide.

l 9326364 -- If two independent dimensions have the same leaf member name for one varyingattribute, deployment fails with the error, "Duplicate name of the field in the query."

For example, suppose there is a varying attribute dimension, "VARYPER," and twoindependent dimensions, "Period" and "Year." If the leaf member name is the same for both"Period" and "Year" in the Essbase Model Properties, Independent Dimension Bindingdialog box, the deployment will fail.

Workaround: Rename the column for the physical relational table that will be used for theleaf member name. If that is not possible, you can create a user-defined table with thedifferent column name and build the second independent dimension based on a column inthe user-defined table.

l 9364712 -- When deploying cubes in nonstreaming mode (the Enable streaming mode forcube deployment check box is cleared), deployment fails when the Essbase model is basedon a Unicode data source.

Workarounds:

m Use streaming mode: In the Cube Deployment Wizard, ensure that the Enable streamingmode for cube deployment check box is selected.

m 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:

o On Windows, use the ODBC Data Source Administrator to create a DSN with theEnable N-CHAR Support option selected. This option is found on the Advanced tabof the ODBC driver setup dialog box.

8

o On UNIX or Linux, edit the odbc.ini file to create a new DSN, and set theEnableNcharSupport value as follows:

EnableNcharSupport=1

Then, the Cube Deployment Wizard, complete these steps:

1. In the Essbase Server connection options page, select the ODBC (Enter ODBC DSNName) option and provide the DSN you created.

2. In the Cube deployment options page, ensure that the Enable streaming mode for cubedeployment check box is cleared.

See the Cube Deployment chapter in the Oracle Essbase Studio User's Guide forinformation on using the Enable streaming mode for cube deployment check box.

l 9433391 -- Deploying From Text File Data Sources

m Cube deployment from text file data sources is always done in nonstreaming mode.

Essbase Studio Server uses the nonstreaming cube building method automatically fortext file data sources; you will not be asked about or notified of this internal load method.

m Cube deployment progress statistics are not supported on text file data sources.

l 9477466 -- In Smart View, when performing drill-through from an Essbase Studio-sourcedcube to Oracle Hyperion Financial Data Quality Management, if the EPM System SingleSign-On token expires before the sessions of all products involved expire (Workspace, OracleHyperion Provider Services, Essbase, Essbase Studio, Oracle Hyperion Financial DataQuality Management), the following message is displayed: “Error: An error occurred loggingon to the system using single sign-on. Please contact your administrator. Error: 2067 - Youdo not have access to the application!”

Workaround: Log in again to Workspace from Oracle Smart View for Office client.

l 9492526, 9502269-- On Windows, when Essbase is started using OPMN, cube deploymentfails for cubes built from Oracle BI EE data sources if the option ODBC (Essbase dynamicallycreates ODBC connection string) is selected in the Cube Deployment Wizard.

Workarounds: For successful deployment, use one of the following workarounds:

m In the Cube Deployment Wizard, specify an ODBC DSN for the OBI data sourceconnection. See “Providing Connection Information for Cube Deployment” in theOracle Essbase Studio User's Guide for more information.

m Check the “Enable streaming mode for cube deployment” option in the CubeDeployment Wizard to start Essbase Studio Server in streaming mode, then performthe deployment.

l 9561925 -- Solaris only: Your machine likely has a network configuration problem if EssbaseStudio Server fails to start, and either of the following messages appears in the server log file:

m Cannot register server in catalog.

m Network error prevented server registration check.

9

Workaround: Manually add a single, empty row to the cp_server_key table in the EssbaseStudio catalog database.

l 11663358 -- Cubes containing calendar hierarchies with day attributes do not correctly buildduring cube deployment as most of the day attributes are missing. (Related to bug 11696797.)

l 11696797 -- The day attributes of a calendar hierarchy are not all listed under the hierarchyin the Essbase Model Properties dialog. (Related to bug 11663358.)

l 13810033 -- Essbase Studio does not support IPv6 protocol on Microsoft Windowsplatforms. Essbase Studio supports IPv6 protocol only on UNIX platforms.

l 14155099, 14462547 -- Netezza Data Source for Essbase Studio. Unable to connect to aNetezza 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 asemicolon (;) comment indicator at the beginning of the data source entry. In the followingexample, 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 notdisabled by the semicolon comment indicator.

Note: The Netezza ODBC driver must be installed on the machine on which Essbase Serverruns.

Tips and Troubleshooting

Limitations and GuidelinesThe Oracle Essbase Studio User's Guide (PDF and HTML format) contains an appendix entitled“Essbase Studio Limitations and Guidelines,” which describes various limitations you mayencounter while working with Essbase Studio.

Also, refer to the “Working with the Virtual Memory Setting” on page 12 section of thisdocument.

10

Setting Non-default Connections to Teradata Data SourcesTo set non-default connection properties to a Teradata data source, add the following line toserver.properties:server.jdbc.teradata.properties=property1=value1,property2=value2...

For example, to specify the character set UTF16, add the line:server.jdbc.teradata.properties=charset=UTF16

Selecting a Language in the Essbase Studio Client InstallerThe Essbase Studio client installer allows you to select a language, however if the system localedoes not match the selected language, the UI in Essbase Studio matches language of the systemlocale and not the language selected in the installer. For example, if you launch the installer andselect the Japanese language on a system with an English locale, the installer displays in Japanese,and Essbase Studio is installed successfully. When you launch Essbase Studio, the UI displays inEnglish.

Verifying Catalog URL Property SyntaxIf Essbase Studio Server fails to start, check the catalog.url property in theShared ServicesRegistry file to verify that the syntax is correct.

If the syntax is incorrect, Essbase Studio Server will not start. If the syntax is incorrect, updatethe catalog.url property in the server.properties file or in Shared Services Registry tocorrect the problem. Then restart Essbase Studio Server.

Notes:

l See the topic, “catalog.url” in the Oracle Essbase Studio User's Guidefor more informationand examples.

l Settings in server.properties override settings in Shared Services Registry.

l To view or modify settings in the Shared Services Registry, use the epmsys_registryutility, described in the Oracle Enterprise Performance Management System DeploymentOptions Guide.

Running the "reinit" Command if Using "Apply MaintenanceRelease" OptionIf you used the “Apply Maintenance Release” option to move from Essbase Studio Release 11.1.2,11.1.2.1 or 11.1.2.2 to this release, you must update the Essbase Studio catalog after installationand configuration. You update the catalog by issuing the reinit command in the Essbase Studiocommand line client. For instructions, see the Oracle Enterprise Performance Management SystemInstallation and Configuration Guide, “Updating the Essbase Studio Catalog.”

11

Support for Incremental Builds of XOLAP ModelsIn the “Limitations and Guidelines” appendix, under “General Limitations” in the “CubeDeployment Limitations and Guidelines” section, the statement, “Incremental builds forXOLAP-enabled models are not supported. ” is incorrect. You can ignore this statement. Startingwith Release 11.1.2.1.102, Essbase Studio supports incremental builds for XOLAP-enabledmodels.

About Essbase Studio Server-Generated MaxL for XOLAPCubes(11058371, 11068896)

You can generate a MaxL deploy statement by choosing options in the Cube DeploymentWizard and then saving your selections as a MaxL script.

When redeploying XOLAP cubes, if you then edit the Essbase Studio Server-generated MaxL toremove 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 StudioServer-generated MaxL script. Instead, Oracle recommends that you launch the Cube DeploymentWizard, make your required selections, then save those selections in a new MaxL script.

Using the MaxL Import Dimensions Statement with EssbaseStudio Rules Files(7216055, 9034403)

You can use the MaxL Deploy statement to load members and data into Essbase from a rulesfile that was created in Essbase Studio. The Deploy statement provides you with the simplestway to accomplish this task.

You may, however, choose to use the MaxL Import Dimensions statement to load membersfrom an Essbase Studio-generated rules file. If you choose to use the Import Dimensionsstatement to build an outline, note that a problem exists when building an Accounts dimensioneither from the fact table or from a hierarchy containing only user-defined members. When thisis 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 ImportDimensions 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';

Working with the Virtual Memory Setting(9460997, 9480016, 10415849)

12

On the machine where Essbase Studio Console is running, you may increase the virtual memorysetting 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 theOracle Essbase Studio User's Guide.

Deploying Cubes Based on Oracle BI EE Data Sources(9492623, 10391499)

Table 2 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 whetherstreaming or nonstreaming mode is supported for a particular operating system. Also, if furtherconfiguration must be completed, there is a reference to the appropriate substep in step 2; forexample, step 2.a or step 2.b.

Table 2 Essbase Studio Server Integration with Oracle BI EE Server

Oracle BI EEVersion

Nonstreaming Mode server.essbase.streamingCubeBuilding=false Streaming Mode server.essbase.streamingCubeBuilding=true

11.1.1.5 or later Windows: Supported

Modify the essbase.cfg file. See step 2.b.

UNIX and Linux: Not Supported

Oracle BI EE ODBC driver has a conflict on common environmentvariables, such as ORACLE_HOME.

Windows: Supported

UNIX and Linux: Supported

See step 2.c.

10.1.3.4 or later Windows: Supported

Requires the Oracle BI EE 11.1.1.5 ODBC driver installed on samemachine 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 11.1.1.3. See step 2.d.

Windows: Supported

UNIX and Linux: Supported

10.1.3.3. orearlier

Windows: Not Supported

UNIX and Linux: Not Supported

Windows: Supported

See step 2.e.

UNIX and Linux: Supported

See step 2.e.

ä To complete any further configuration required by Table 2:

1 On Windows, in nonstreaming mode (in Essbase Studio Console, in the Essbase Server connectionoptions dialog of the Cube Deployment Wizard, select “Enable streaming mode for cube deployment.”)Essbase Studio can deploy cubes from Oracle BI EE data sources version 10.1.3.4.1 or later, as longas the Oracle BI EE ODBC driver is version 11.1.1.5 and resides on the same machine as the EssbaseServer.

13

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 nonstreamingmode:

a. Uncomment the ;BPM_ORACLEBI_DriverDescriptor "Oracle BI Server11g_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 theODBC 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.5or higher, you must use streaming mode.

d. UNIX and Linux, in nonstreaming mode, when deploying cubes based on Oracle BI EEversion 10.1.3.4 data sources, you must add the following environment variables to theopmn.xml file:

<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 andOracle BI EE Integration” in the Oracle Enterprise Performance Management SystemInstallation and Configuration Guide.

e. On Windows, UNIX, and Linux, cubes may be deployed based on Oracle BI EE version10.1.3.3 only if streaming mode is enabled.

3 ODBC driver configuration for Oracle BI EE running on UNIX is covered in the topic, “(UNIX) Configuringthe Environment for Essbase and Oracle BI EE Integration,” in the Oracle Enterprise PerformanceManagement System Installation and Configuration Guide.

“Inconsistent Object in Catalog” Error During Upgrade(11073948)

When upgrading from Release 11.1.1.3, during configuration with Oracle Hyperion EnterprisePerformance Management System Configurator, if the Configure Database task fails for EssbaseStudio, 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 theEssbase Studio catalog is successfully upgraded.

14

This error occurs when you rename data source connections which have drill-through reportsdependent 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. Fixinconsistent drill-through reports (drill-through reports that depend on data source connectionsthat have been renamed) by taking any of these actions:

l In the 11.1.1.3 environment, rename the data source connections back to their originalnames.

l 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.

l Delete the invalid drill-through reports from the 11.1.1.3 environment and then recreatethem in the upgraded Essbase Studio environment, if needed.

Then, restart EPM System Configurator and rerun the Configure Database task.

Starting Essbase Studio Server with Windows Authentication(13562254)

When Essbase Studio Server is installed and configured as a Windows service, you cannot startit as a service using Windows authentication. In order configure Essbase Studio Server to takeadvantage of Windows authentication, you must do the following:

1. If already running, stop the Essbase Studio Server service.

2. Add the catalog.username property to the server.properties file as follows:

catalog.username=

Do not add any user name or other text to the catalog.username property.

3. Start Essbase Studio Server using either the Start menu or thestart_BPMS_bpms<instance>_Server.bat file.

Oracle Advanced SecurityIf you are using an Oracle database with Essbase Studio, you may want to configure the associatedOracle JDBC drivers with Oracle Advanced Security. Click the following link for informationon Oracle Advanced Security:

http://download.oracle.com/docs/cd/B19306_01/network.102/b14268/asojbdc.htm#i1006717

15

Documentation Updates

Accessing EPM System Product DocumentationThe most recent version of each EPM System product guide is available for downloading orviewing from the EPM System Documentation area of the OTN website (http://www.oracle.com/technology/documentation/epm.html). You can also use the EPM SystemDocumentation Portal (http://www.oracle.com/us/solutions/ent-performance-bi/technical-information-147174.html), which also links to EPM Supported Platform Matrices, My OracleSupport, and other information resources.

Deployment-related documentation is also available from the Oracle Software Delivery Cloudwebsite (http://edelivery.oracle.com/EPD/WelcomePage/get_form).

Individual product guides are available for download on the Oracle Technology Network websiteonly.

Copying and Pasting Code Snippets from PDFsWhen you cut and paste code snippets from a PDF file, some characters can be lost during thepaste operation, making the code snippet invalid. Workaround: Cut and paste from the HTMLversion of the document.

Documentation FeedbackSend feedback on product documentation to the following email address:

EPMdoc_ww@oracle.com

Follow EPM Information Development on these social media sites:

l YouTube - http://www.youtube.com/user/OracleEPMWebcasts

l Google+ - https://plus.google.com/106915048672979407731

l Twitter - https://twitter.com/HyperionEPMInfo

l Facebook - https://www.facebook.com/pages/Hyperion-EPM-Info/102682103112642

l Linked In - http://www.linkedin.com/groups?home=&gid=3127051&trk=anet_ug_hm

Accessibility ConsiderationsOur goal is to make Oracle products, services, and supporting documentation accessible to thedisabled community. EPM System products support accessibility features, which are describedin the product's Accessibility Guide. Find the most up-to-date version of this guide in the EPMSystem 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.

16

Minischemas are only a graphical representation of a datasourceMinischemas are only a graphical representation of information about a data source. Thisinformation remains in the Essbase Studio catalog regardless of the state of the minischema.When a minischema is manually recreated after an upgrade to a new release, all Joins that existin the previous release will be displayed properly. (17859852)

Essbase Studio RolesIn the Release 11.1.2.3.000 Oracle Hyperion Enterprise Performance Management System SecurityAdministration Guide, in the Essbase Studio Roles topic, two of the roles are reversed. The rolesare described like this:

l Essbase Studio Data Source Administrator - Performs all tasks related to metadata elementcreation and maintenance; deploys cubes; executes drill-through reports.

l Essbase Studio Metadata Administrator - Performs all tasks related to data sourceconnection creation and maintenance; executes drill-through reports.

They should be described like this:

l Essbase Studio Data Source Administrator - Performs all tasks related to data sourceconnection creation and maintenance; executes drill-through reports.

l Essbase Studio Metadata Administrator - Performs all tasks related to metadata elementcreation and maintenance; deploys cubes; executes drill-through reports.

Importing a Catalog Export FileYou can import a catalog export file from the current release or one major release prior to thecurrent release.

Turning off Validation of Custom SQL for Data Load SettingsA new server property, server.query.skipValidation (true | false) can be used toskip validation of Custom SQL for data load settings. You may want to use this setting if it takesa long time to close the Define Data Load Settings dialog box. To turn off validation of CustomSQL, enter server.query.skipValidation=true in the server.properties file.

Restructuring User Data Source Permissions for User-Defined QueriesFor user-defined SQL queries from Essbase Studio, the data source administrator must ensurethat data source users only have permissions to read the data of the tables that they require, and

17

no more. This will prevent users from potentially running queries that access data to which theyare not entitled.

Enabling Streaming ModeDo not use the server.properties setting, server.essbase.streamingCubeBuildingto enable streaming mode. Instead, in Essbase Studio Console, in the Essbase Server connectionoptions dialog of the Cube Deployment Wizard, select “Enable streaming mode for cubedeployment.” The “Enable streaming mode for cube deployment” setting overrides theserver.essbase.streamingCubeBuilding server.properties setting.

New Default Essbase Studio HTTP PortThe default HTTP port for Essbase Studio has been changed to 12080 from 9080.

Limiting Permissions for the Data Source UserIn the Oracle Essbase Studio User's Guide, in the “Limitations and Guidelines” appendix, under“Catalog and Data Source Guidelines,” in the “User Defined SQL Validation” section, thestatement “It is the Essbase Studio administrator’s responsibility to limit permissions for thedata source user” is incorrect. Instead, it should say “It is the database administrator’sresponsibility to limit permissions for the data source user.”

Configuring Teradata as a Data Source

ä To configure Teradata as a data source:

1 Install Teradata drivers, which you must obtain from Teradata.

l Essbase Studio uses JDBC drivers. The JDBC Teradata driver must be installed on thecomputer 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 installedon the computer on which Essbase Server runs.

l Essbase uses ODBC drivers. The ODBC Teradata driver must be installed on thecomputer on which Essbase Server runs.

2 Stop Essbase from the Windows Services panel using the Oracle Process Manager and NotificationServer (OPMN) service: EPM_epmsystem1.

3 Backup the OPMN configuration file (opmn.xml).

For example:

C:\Oracle\Middleware\user_projects\epmsystem1\config\OPMN\opmn\opmn.xml

4 Open the opmn.xml file in a text editor.

18

5 To properly load the Teradata drivers, the opmn.xml file must include a statement that points to thelocation of the Teradata libraries.

a. Locate the following statement in the opmn.xml file:

<variable id="ESS_CSS_JVM_OPTION7" value="-Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration"/>

b. After this statement, add a statement similar to the following one:

<variable append="true" id="PATH" value="C:\Program Files\Teradata\Client\14.00\Shared ICU Libraries for Teradata\lib"/>

6 When using Teradata data sources with Essbase, and using OPMN to monitor and control the EssbaseAgent process, you must update the opmn.xml file with variables for the operating system you areusing.

Note: The absolute path value cannot contain spaces. The examples of absolute path valuesare based on a 64-bit machine configuration.

64-bit Windows

Add these variables:

l TWB_ROOT: Teradata root

l PATH: Teradata shared libraries

l PATH: Teradata client DLL libraries

l PATH: Teradata Call-Level Interface Version 2 routines

l 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"/>

64-bit AIX

Add these variables:

l LIBPATH: Teradata ODBC libraries

l LIBPATH: Teradata shared libraries

l LIBPATH: ODBC components needed to load Teradata ODBC drivers

l LIBPATH: Teradata client libraries

l COPERR: Directory where the errmsg.txt file resides

l NLSPATH: Teradata message libraries

19

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"/>

64-bit LINUX

Add these variables:

l TWB_ROOT: Teradata root

l TD_ICU_DATA: Teradata shared libraries

l NLSPATH: Teradata ODBC message libraries

l COPERR: Directory where the errmsg.txt file resides

l COPLIB: Directory where the libcliv2.so library file resides

l LD_LIBRARY_PATH: Teradata libraries

l PATH: Teradata client directories

Note: 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/>

7 Save the opmn.xml file.

8 Start Essbase from the Windows Services panel using the Oracle Process Manager and NotificationServer service (EPM_epmsystem1).

9 Verify the following:

l Essbase: Use the Data Prep Editor in Administration Services Console to connect to aTeradata database using a DNS.

l Essbase Studio: Perform a cube deployment in non-streaming mode, which uses theTeradata ODBC driver.

20

Administrator Privileges Required for Catalog Export/ImportTo perform an export/import of the Essbase Studio catalog database, you must be provisionedas Administrator in Oracle Hyperion Shared Services. For information on provisioning and onall Essbase Studio roles, see the Oracle Essbase Studio User's Guide.

Previously Undocumented Rules for Drill-through TemplateSQLThe following rules for drill-through template SQL were not previously documented:

l All pairs of predefined variables that are associated with dimension intersection values anddimension table columns must be included in the user-defined SQL. For example, theintersection of the dimension Product is specified by the following expression in the standardSQL template:

$$Product-COLUMN$$ IN ($$Product-VALUE$$)

This expression must also be included in the user-defined SQL template.

l In the user-defined SQL template, users should reuse the same alias names that weregenerated by the Essbase Studio Server in the predefined SQL template.

Support for Incremental Builds of XOLAP ModelsIn the “Limitations and Guidelines” appendix, under “General Limitations” in the “CubeDeployment Limitations and Guidelines” section, the statement, “Incremental builds forXOLAP-enabled models are not supported. ” is incorrect. You can ignore this statement. Startingwith Release 11.1.2.1.102, Essbase Studio supports incremental builds for XOLAP-enabledmodels.

Update to Topic, "Upgrading the Essbase Studio Catalog andData"(10383674, 10647506)

The topic, “Upgrading the Essbase Studio Catalog and Data” has been updated. Please disregardthe topic in the Oracle Essbase Studio User's Guide and refer to the topic below.

Upgrading Essbase Studio

To move Essbase Studio from release 11.1.1.3 to the 11.1.2.3 release, you perform an upgrade.To move from release 11.1.2.x to 11.1.2.3, you apply the maintenance release.

The upgrade or maintenance release procedure for Essbase Studio is part of the configurationprocess for Oracle Enterprise Performance Management System. See the Oracle EnterprisePerformance Management System Installation and Configuration Guide for more information.Complete the tasks applicable to your environment in the order noted in the guide.

21

After configuration, perform these tasks in Essbase Studio:

1. If Essbase Server has moved, perform the rehosting procedure so that Essbase connectionspoint to the new server location, as described in “Updating References to Rehosted EPMSystem Products” in the Oracle Essbase Studio User's Guide.

2. If Essbase Studio Server has moved, for deployed applications that reference the old serverlocation, update the cube linkage, as described in “Updating Cube Linkage” in the OracleEssbase Studio User's Guide.

3. For text file data sources:

l Specify either the location from an earlier release, or the replicated location for theEssbase Studio data files by modifying the default EPM_ORACLE_INSTANCE/BPMS/bpms1/datafiles location provided in the Oracle Hyperion Enterprise PerformanceManagement System Configurator. See the Oracle Enterprise Performance ManagementSystem Installation and Configuration Guide for more information.

l Edit the connection properties for any text file connections to point to the new locationof the text files, as described in “Editing Data Source Connection Properties” in theOracle Essbase Studio User's Guide.

l After configuration, if you move your text files to another location, edit theserver.datafile.dir property in the Shared Services Registry and edit theconnection properties for any text file connections to point to the new location of thetext files. See “server.datafile.dir” and “Editing Data Source Connection Properties”respectively in the Oracle Essbase Studio User's Guide.

To view or modify settings in the Oracle Hyperion Shared Services Registry, use theepmsys_registry utility, described in the Oracle Hyperion Enterprise PerformanceManagement System Installation and Configuration Guide

4. If Performance Management Architect Dimension Server has moved, edit the connectionproperties for any Performance Management Architect Dimension Server connections thatpoint to the old server location, as described in “Editing Data Source Connection Properties”in the Oracle Essbase Studio User's Guide.

Previously Undocumented User Role, cpDMDSAdmin(11724835)

The Essbase Studio user role, cpDMDSAdmin, was previously undocumented. This role has allthe privileges of the Essbase Studio Viewer, Data Source Administrator, and MetadataAdministrator roles. The cpDMDSAdmin role name appears in the title bar of the Essbase StudioConsole when both the Data Source Administrator and Metadata Administrator roles areselected when provisioning.

For information on provisioning and on all Essbase Studio roles, see the Oracle EnterprisePerformance Management System User Security Administration Guide.

22

Inconsistent Member Sort Order When Prefix/SuffixTransformations Are Applied(12815260)

When dimension elements have sort orders applied to them and, in the Essbase model, themembers based on those dimension elements have prefix or suffix transformations applied tothem, 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 ordersapplied to the underlying dimension element, you can edit the key binding expression for theelement to add the transformation. Do not use the transformation functionality in the Essbasemodel 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 elementproperties are set as follows:

l Dimension element FAMILY—with Key and Caption Bindings set toPRODUCTDIM.FAMILY, and Sort Column set to PRODUCTDIM.FAMILY

l Dimension element SKU—with Key and Caption Bindings set to PRODUCTDIM.SKU, andSort 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 dimensionelement, 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'

Issues Related to Essbase Model Resync

Removing Base Chain in Hierarchy Causes Cube Deployment to Fail(12988552)

In a multichain hierarchy containing a base chain and attribute chains, when removing the basechain, the Essbase model resync operation will succeed, but cube deployment of this model willfail.

Note that the Essbase model resync operation does not validate the model. If the resynced modelcontains errors, you will not be notified. Therefore, you must validate the model separately byopening it in the Essbase Model Properties dialog box and performing the steps in the “ValidatingModel Properties” topic in the Oracle Essbase Studio User's Guide.

23

Attribute Settings Deleted When Adding or Removing an Intermediate Levelin a Hierarchy(13005538)

In a multichain hierarchy containing a base chain and an attribute chain, if an intermediate levelin an attribute chain is added or deleted and then model resync is performed, the attributesettings 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 Essbasemodels. Also, Oracle recommends that you validate the model before attempting cubedeployment.

Resync Indicates Success, But Varying Attribute Settings Do Not Work(13601134)

If you remove the leaf level of a hierarchy that is included in a varying attribute, and then performa model resync, the resync will appear to be successful but the varying attribute will no longerwork. Deployment of a cube that uses this hierarchy will fail.

As stated in the previous item (13005538), after performing the model resync, review and, wherenecessary, reset attribute or varying attribute properties in affected Essbase models. Also, be sureto validate models before attempting cube deployment.

Operations that Do Not Trigger a Model Resync(13706843)

In the topic, “About Model Resync,” there are two erroneous items in the list of operations thattrigger the need for a model resync. Those operations are:

l Renaming the schema

l Renaming the hierarchy

Note that renaming a cube schema or a hierarchy does not trigger the need for a model resync.

Drill-through Preview Maximum Rows Allowed(13633757)

When previewing drill-through reports in Essbase Studio, the maximum number of rowsreturned is 1024.

Note: You preview, or test, drill-through reports by clicking the Test button in the ReportContents tab of the drill-through report editor.

24

Default Settings for Essbase Models Based on Oracle BI EEBusiness Model Option(13578402, 16653895)

When working with an Essbase model that is based on an Oracle BI EE data source using theBusiness Model option, and you selected the Create cube schema and Essbase model optionwhen creating the data source connection, then the ASO storage model option and Duplicatemember name support option are enabled by default. You may clear the ASO storage modeloption if necessary.

Deployments from Oracle Business Intelligence Enterprise Edition data sources must be builtusing the Duplicate member name support option.

Updates to “Starting and Stopping Essbase Studio Server andConsole” Topicl This topic references the EASLaunch.properties file in error. Administration Services

Console can no longer be launched from Essbase Studio Console and, therefore, this file hasbeen removed from the installation.

l 13560119 -- When using scripts to start or stop Essbase Studio Server, be sure to use ONLYthe .bat or .sh scripts located in EPM_ORACLE_INSTANCE/bin.

Do not use the .bat or .sh files that are located in EPM_ORACLE_HOME/products/Essbase/EssbaseStudio/Server to start or stop the Essbase Studio Server.

New Comments Options Group for Members in EssbaseModels(13694485)

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 beenconverted to a new Comments group with these options:

l Comments—a text box where you enter a comment for the member.

l From External Source—a drop-down list box where you select an applicable database columnthat contains comments, which are loaded along with members during cube deployment.

You can select one of the above options per member.

Erratum: Drill-Through C APIs Not Supported with EssbaseStudio(21264590) The following erratum applies to all 11.1.2.3.x and 11.1.2.4.x releases, and beyond.

25

The following Oracle Essbase C API functions are not supported with Oracle Essbase Studiodrill-through.

l EssGDTConnect

l EssGDTRequestDrillThrough

l ESSGDTGetInfo

l ESSGDTSetInfo

l ESSGDTListReports

l EssGDTExecuteReport

l EssDTAPIGetError

l ESSGDTGetHeader

l ESSGDTGetData

l EssGDTEndDrillThrough

26

27

COPYRIGHT NOTICE

Essbase Studio Readme, 11.1.2.3.000

Copyright © 2014, 2016, Oracle and/or its affiliates. All rights reserved.

Updated: June 2016

Authors: EPM Information Development Team

This software and related documentation are provided under a license agreement containing restrictions on use and disclosureand are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, youmay not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or displayany part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless requiredby law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find anyerrors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S.Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS:

Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/ordocumentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable FederalAcquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, andadaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights aregranted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developedor intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe,backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability forany damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respectiveowners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under licenseand are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteronlogo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.Microsoft Windows, PowerPoint, Word, Excel, Access, Office, Outlook, Visual Studio, Visual Basic, Internet Explorer, ActiveDirectory, and SQL Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

This software or hardware and documentation may provide access to or information about content, products, and servicesfrom third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kindwith respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between youand Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to youraccess to or use of third-party content, products, or services, except as set forth in an applicable agreement between you andOracle.