Oracle® Essbase Integration Services



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

Authors: EPM Information Development Team

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

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by 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 any errors, 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, the following notice is applicable:


Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or 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 for any damages caused by use of this software or hardware in dangerous applications.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Table of Contents:


Installation Information

Supported Platforms

Supported Languages

Supported Paths to this Release

Defects Fixed in this Release

Known Issues

Tips and Troubleshooting

Documentation Updates

Accessibility Considerations


This document includes important, late-breaking information about this release of Oracle Essbase Integration Services. Review this Readme thoroughly before installing Integration Services.

Installation Information

Late-breaking information about installation of Oracle Enterprise Performance Management System products is provided in the Oracle Enterprise Performance Management System Installation and Configuration Readme. Review this information thoroughly before installing EPM System products.

Supported Platforms

Information about system requirements and supported platforms for EPM System products is available in a spreadsheet format in the Oracle Enterprise Performance Management System Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on the Oracle Technology Network (OTN):

Note that XML Import/Export and sample application creation are not supported on the following platforms:

  • UNIX 64-bit

  • Windows 2008 64-bit

  • IBM DB2 when used on Windows 2003 64-bit

Supported Languages

Information about supported languages for EPM System products is available in a spreadsheet format on the Translation Support tab in the Oracle Enterprise Performance Management System Certification Matrix. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on OTN:

Supported Paths to this Release

You can upgrade to EPM System Release from the following releases:


For instructions to upgrade, see the Oracle Enterprise Performance Management System Installation and Configuration Guide, "Upgrading EPM System Products."

Table 1. Supported Paths to this Release

Release Upgrade Path FromTo



When moving from Release or to Release, you use the "Apply Maintenance Release" option in Oracle Hyperion Enterprise Performance Management System Installer, instead of following the documented upgrade procedures.

For Oracle Hyperion Financial Close Management, applying the maintenance release is supported only from Release



If you were using Oracle Hyperion EPM Architect Release 9.3.1, you can download the Oracle Hyperion Shared Services release 9.3.3 from My Oracle Support.

A release earlier than Release 9.3.3.x

If you are upgrading from a release earlier than 9.3.3.x, you must first upgrade to a supported release and then upgrade to release For upgrade procedures for the earlier release, see the product installation guides for the interim release that you are upgrading to.

An environment that includes multiple releases, which can include an environment with one instance of Shared Services or an environment with two instances of Shared Services

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


If you are starting from Release, 9.3.0.x, 9.3.1.x (except for Oracle Essbase,,, and, or 11.1.1.x, Oracle recommends that you upgrade to Release as your interim release. If you are starting from an earlier release, Oracle recommends that you upgrade to the highest level release that directly supports upgrade from your starting release. Security Synchronization between Essbase and Shared Services was removed in Essbase Release 9.3, starting with Release Essbase and Oracle Hyperion Shared Services Release, however, still synchronize security information. For this reason, if you are using Essbase Release,,, or, you must first upgrade all products to Release 9.3.3, instead of Release

Defects Fixed in this Release

If you are coming from Release or, use the Defects Fixed Finder tool to review the list of defects fixed between those releases and Release This tool is available here:

  • 13471002 -- From the Drill-Through Reports dialog box, when making a copy of an existing drill-through report, the report does not copy completely. The OLAP Intersection Levels and the Drill-Through Report Columns lists are empty.

Known Issues

The following issues are the noteworthy known issues of this patch.

  • N/A -- DB2 OS/390 is supported only as a data source and should not be used as an OLAP Metadata Catalog. If you use IBM DB2 OS/390 as a data source, you must add an entry to the ais.cfg file for each data source name you configured in your DataDirect Wire Protocol driver for DB2. Add an entry to the ais.cfg file in the following format:


    For example, using the sample database, TBC, the following is the entry to the ais.cfg file:

  • N/A -- Note the following regarding ODBC:

    • “Localhost” is not a valid server name. In the Login dialog box, you must specify a computer name or IP address in both the Integration Server frame and the Essbase Server frame.

    • For UNIX systems, Integration Services installation creates a template odbc.ini. To store information about how to connect to a relational data source, edit the file using your preferred editor.

    • To configure a Teradata data source, the TDODBC environment variable must be set manually.

  • N/A -- Multibyte-character-set characters should not be used in the names of OLAP models, metaoutlines, data sources, and owners.

  • N/A -- If you run Integration Services on Windows and access an Oracle database as an MBCS or Unicode data source using the DataDirect Wire Protocol Driver, characters corresponding to 0x4E88 in UTF-8 encoding may not be processed properly.

  • N/A -- Due to database restrictions in some databases such as Oracle, if the IN clause has more than 1,000 outline members that require updating during time-based incremental loads, SQL statements may not execute. In such cases, we recommend full loads rather than time-based incremental loads.

  • N/A -- Although Oracle Essbase Administration Services validates recently added functions in formulas for the block storage option (BSO), Integration Services may not. We strongly recommend you use Oracle Essbase Administration Services to validate these functions.

  • N/A -- If you use Japanese encoding, Oracle recommends you use MS932 encoding instead of Shift-JIS.

  • N/A -- If you customize drill-through reports at run time and add a user-defined filter, keep the length of the filter under 8KB; otherwise, some members may not be included in the drill-through report query.

  • N/A -- To verify member formulas, users must have “Create” access to the Essbase Server.

  • N/A -- Drill-through operations are not supported on Unicode data in release 11.1.2.

  • N/A -- The current batch files and scripts used to create the TBC sample tables and to load the sample data do not function with SQL Server 2005. These files require the executable named SQLCMD.EXE. Workaround: Edit the batch file install_sqlsrv.bat located in the AIS\samples directory, and replace the name of the executable ISQL.EXE with the new executable name SQLCMD.EXE.

  • N/A -- When managing Oracle’s Hyperion Shared Services models and naming applications, you cannot use the forward slash (/), backslash (\), or double quotation (“) characters.

  • N/A -- Oracle recommends that your users be granted read-only permission to external data sources for drill-through reports and custom data load SQL.

  • N/A -- If you are using Windows Server 2003 Service Pack 1 with Integration Services, your system may experience an abnormal shutdown. To prevent this, install the update from Microsoft by going to:

  • N/A -- Integration Services does not support updating drill-through information in an outline containing duplicate member names. For such outlines, you should perform a full member load.

  • N/A -- If the Time dimension is built directly from the fact table, and you select an alternate fact table, the data load may reject those records for which time members are not found in Essbase. In such cases, be sure that the time dimension is built to span time periods of all fact tables.

  • 6536313 -- When using the Drill-Through Wizard in Oracle Essbase Spreadsheet Add-in, users will only see the first 80 characters of the table or column name.

  • 6551802 -- If column names contain 0x5C double-byte characters, the columns may not display in a table.

  • 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, including Integration Services, does not support the JISX0213 Japanese character set.

  • 6584211 -- When building a shared hierarchy for a block storage database, adding a shared hierarchy a second time may duplicate the values stored on a single element, resulting in incorrect data. This problem occurs when shared members are from the same hierarchy, such as these two hierarchies from the TBC sample database: Diet > 100-20 and 100 > 100-20.

    Workaround: Use user-defined SQL to edit data load commands.

  • 7253757 -- On Windows 2003 SP1, after installing Integration Services, the Oracle Hyperion Enterprise Performance Management System Installer uses Windows services to start and stop the services for Integration Services Sometimes after stopping the service using Windows Services console, the Integration Server process, olapisvr.exe, continues to run.

    Workaround: Manually stop the olapisvr.exe and olapisvc.exe processes by using the Windows Task Manager.

  • 7386388 -- Data is not available in Excel although Integration Services Console indicates a successful data load.

    Workaround: Perform the data load twice.

  • 7482771 -- Using the INCRESTRUC setting in the essbase.cfg file when performing an incremental restructuring does not work on large outlines. The outline must have less than 2 billion possible blocks for Oracle Essbase to allow for incremental restructuring. The number of possible blocks is equal to the number of members in each SPARSE dimension multiplied with each other. For example, consider an outline with five dimensions, and the number of members in each dimension is 50, 10, 100, 1000, and 10,000. If the first dimension is dense and all other dimensions are sparse, then the total number of possible blocks is 10 billion (10*100*1000*10,000).Incremental restructure is not possible in this example. However, if both the first and second dimensions are dense, the number of possible blocks is 1 billion. Incremental restructure is possible.

  • 7831887 -- Integration Services does not support connections to Shared Services. Attempting to connect to Shared Services will result in the error message, “JAVA.LANG no such method.”

  • 9320561, 10320758, 13654820 -- XML Import/Export and sample application creation are not supported on the following platforms:

    • UNIX 64-bit

    • Windows 2008 64-bit

    • IBM DB2 when used on Windows 2003 64-bit

  • 9354454 -- When Integration Server is started before the crontab file is created, operations such as data loads may fail, and the error number OLAPISVR 2001011 is displayed. (Missing error text reads, “Cannot open a file in the crontabs directory.” )

    Workaround: Before starting Integration Server, issue a “crontab – e” command to create the crontab file. Save the crontab file and then start the server.

  • 9956385 -- When creating an OLAP Metadata Catalog, ODBC errors may appear in the olapisvr.log file even though catalog creation was successful. The bolded lines below are examples of the types of ODBC errors you might see in olapsvr.log:

    [DataDirect][ODBC SQL Server Native Wire Protocol driver][Microsoft SQL Server] Invalid object name 'OM_DESCRIPTIONS'.  
    [DataDirect][ODBC SQL Server Native Wire Protocol driver][Microsoft SQL Server] Invalid object name 'OM_INFO
  • 10073704 -- Hybrid Analysis is not supported on aggregate storage databases. Note that the Integration Services Console does not prevent you from enabling a metaoutline for aggregate storage, even when it contains members that are enabled for Hybrid Analysis.

  • 13720788 -- After successfully logging into Integration Services, a read lock error occurs when trying to launch an OLAP model or metaoutline. The error message reads, “Failed to set a read lock”.

    Workaround: To correct this problem, you must implement a connection option, “TimestampTruncationBehavior” as described in Oracle Only: OLAP Model or Metaoutline Read Lock Error in the Tips and Troubleshooting section.

  • 13696003 -- The member and data load scheduling functionality in Integration Services Console does not work in a Windows 2008 on 64-bit environment.

    Workaround: Use the Save Script functionality in the Member and Data Load dialog box to create a CBS script. Then use Windows Task Scheduler to run the script.

Tips and Troubleshooting

Oracle Only: OLAP Model or Metaoutline Read Lock Error


After successfully logging into Integration Services, a read lock error occurs when trying to launch an OLAP model or metaoutline. The error message reads, “Failed to set a read lock”.

To correct this problem, a connection option, “TimestampTruncationBehavior” must be implemented as follows:

Windows: To add the connection option to the data source listing in the Windows Registry:

  1. Launch the Windows Registry Editor.

  2. Navigate to HKEY_LOCAL_MACHINE, then SOFTWARE, then ODBC, then ODBC.INI.

  3. Locate and select an Oracle data source, then select Edit, then New, and then String Value.

  4. Overwrite the Name field with the following:

  5. Right-click the line you just added, and then select Modify.

  6. In the Value data text box, enter 1.

  7. Save the entry, and exit the Windows Registry.

UNIX: To add to the connection string to a DSN entry in the odbc.ini file:

  1. On the computer running Integration Server, open the odbc.ini file by using a text editor such as vi.

  2. Locate an Oracle DSN entry to edit.

  3. Add the following line to the Oracle DSN entry:


    For example:

    Description=DataDirect 6.1 Oracle Wire Protocol
  4. When finished, save the odbc.ini file and exit the text editor.

Other Tips

  • Integration Services supports full Unicode functionality only on Oracle relational database servers.

  • Oracle recommends you use the same language for your Data Source Names (DSNs) as you use for your applications. (English will work in all cases.)

  • When creating a drill-through report with an OLAP intersection level based on a user-defined dimension or column, neither of the variables of the form $$dimension-COLUMN$$ or $$dimension-VALUE$$ will be created.

Documentation Updates

Accessing EPM System Product Documentation

The most recent version of each EPM System product guide is available for downloading or viewing from the EPM System Documentation area of the OTN Web site ( You can also use the Oracle Enterprise Performance Management System Documentation Portal (, which also links to EPM Supported Platform Matrices, My Oracle Support, and other information resources.

Deployment-related documentation is also available from the Oracle Software Delivery Cloud Web site (

Individual product guides are available for download on the Oracle Technology Network Web site only.

Accessing the Integration Services Console Help

Windows Vista and later versions of Windows do not include the WinHlp32.exe file. This file must be installed in order to open and view the online help (HLP and CNT files).

To obtain and install the WinHlp32.exe file directly from Microsoft, go to this link:

Copying and Pasting Code Snippets from PDFs

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.

Oracle Call Interface No Longer Supported

Oracle Essbase Integration Services no longer supports Oracle Call Interface (OCI). References in the documentation to OCI should be disregarded.

Displaying Recently Used OLAP Models and Metaoutlines in the File Menu


Recently used OLAP models and metaoutlines no longer display in the File menu of the Integration Services Console.

To view all OLAP models and metaoutlines, select File, and then Open. The Existing tab of the Welcome dialog box is displayed where you will find listed all OLAP models and metaoutlines associated with the OLAP Metadata Catalog to which you are connected.

Accessibility Considerations

It is our goal to make Oracle products, services, and supporting documentation accessible to the disabled community. This Readme file is accessible in HTML format.