Oracle Essbase Integration Services

Release 11.1.2.0.00

Readme
[Skip Navigation Links]

Purpose................................................................................................................................. 1 Installation Information........................................................................................................ 2 Known Issues........................................................................................................................ 2 System Limitations................................................................................................................ 5 Defects Fixed in This Release ................................................................................................ 5 Documentation Updates ........................................................................................................ 6

Purpose
This document includes important, late-breaking information about this release of Oracle Essbase Integration Services. Review this Readme thoroughly before installing Integration Services. This release is intended for new deployments only. Upgrading or migrating from previous EPM System releases is not supported. In addition, products from this release are not compatible with products and applications from previous releases. There have been significant changes to the deployment architecture for this release. A brief summary is provided here but for a complete list, see New Features and General Installation Information in the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Readme. The EPM System directory structure has changed significantly. The default directories are now Middleware Home and EPM Oracle Home. EPM System Installer now installs WebLogic Server (replaces Apache Tomcat as the embedded Java container) and Oracle HTTP Server (replaces Apache Web Server as the embedded Web server). The manual deployment process is greatly simplified, using the Fusion Middleware Configuration Wizard (deployed with WebLogic) to manually deploy Web applications. The Shared Services relational database is now used as Native Directory (replaces OpenLDAP as the central storage for native EPM System user accounts and provisioning information). The new Foundation Services Web application is deployed to one managed server and includes these Web applications: Shared Services and EPM Workspace.

This release supports non-English languages. The list of supported languages for all EPM System products is included in the Oracle Hyperion Enterprise Performance Management System Certification Matrix, posted at: http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html. Top of Document

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

Known Issues
The following issues are the noteworthy known issues of this release. Defect Number 6536313 6551802 6576813 Known Issues When using the Drill-Through Wizard in Essbase Spreadsheet Add-in, users will only see the first 80 characters of the table or column name. If column names contain 0x5C double-byte characters, the columns may not display in a table. The JISX0213 Japanese character set, which replaces the JISX0208 and JISX0212 Japanese character sets, is supported on Windows Vista. The Oracle Essbase family of products, including Integration Services, does not support the JISX0213 Japanese character set. 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. 7386388 Data not available in Excel although Integration Services Console indicates a successful dataload. 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 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. On 64-bit machines, creating a sample application causes a Java run time error and fails because jdbcodbc libray is not loaded. For the same reason, XML Import/Export does not function. Contact your Integration Services administrator because the Java runtime environment may not be set appropriately on the server machine. 2

6584211

9320561

Defect Number 9354454

Known Issues When the Integration Services server is started before the crontab file is created, operations such as dataloads 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 the Integration Services 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'.

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: [DS:dsn:390]. For example, using the sample database, TBC, the following is the entry to the ais.cfg file: [DS:TBC:390] 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

N/A N/A

Multibyte-character-set characters should not be used in the names of OLAP models, metaoutlines, data sources, and owners 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. 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. 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. If you use Japanese encoding, Oracle recommends you use MS932 encoding instead of Shift-JIS.

N/A

N/A

N/A

Defect Number N/A

Known Issues 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. To verify member formulas, users must have Create access to the Essbase Server. Drill-through operations are not supported on Unicode data in release 11.1.2. 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 N/A N/A

N/A N/A N/A

When managing Oracles Hyperion Shared Services models and naming applications, you cannot use the forward slash (/), backslash (\), or double quotation () characters. Oracle recommends that your users be granted read-only permission to external data sources for drill-through reports and custom data load SQL. 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: http://support.microsoft.com/kb/923996/ On Windows 2003 SP1, after installing Integration Services, the EPM 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. (7253757)

N/A

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. 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 Oracle Essbase. In such cases, be sure that the time dimension is built to span time periods of all fact tables.

N/A

Top of Document

System Limitations
The following issues are the noteworthy known system limitations of this release. Defect Number N/A N/A N/A System Limitations Integration Services supports full Unicode functionality only on Oracle relational database servers. Oracle recommends you use the same language for your Data source names 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 userdefined dimension or column, neither of the variables of the form $$dimensionCOLUMN$$ or $$dimension-VALUE$$ will be created. Top of Document

Defects Fixed in This Release

Defect Number 7378293 7420035 7559453 8304260 8309113 8329903 8868519 9083714 Defects Fixed In This Release Member loads and data loads from two different data sources fail. Integration Services hangs in production environment because of RDBMS utility. A compression dimension is not applied to the Product dimension after being applied to the Accounts dimension following a dataload or member load. Dataloads into an aggregate-storage-option (ASO) cube fails when the dataload is run from a cube building script (CBS) script. Decimal data from RDBMS is not loaded in Integration Services when there are null columns in a row. Message for error 2004002 (re: invalid model) contains no text. Integration Server 11.1.1.2 inserts the character M at the end of every line in the /sample/tbcdbase scripts. Integration Services Console disappears if Use Alternate Fact Table is selected during a data load. Top of Document

Documentation Updates
System Requirements
Information about system requirements for EPM System products is now available in a spreadsheet format in the Oracle Hyperion Enterprise Performance Management System Certification Matrix. System requirements are no longer part of the Oracle Hyperion Enterprise Performance Management System Installation Start Here. This matrix is posted on the Oracle Fusion Middleware Supported System Configurations page on OTN (listed in the Oracle Business Intelligence product area): http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

Accessing Hyperion Product Documentation

The most recent version of each Hyperion product guide and online help is available for download from the Enterprise Performance Management System Documentation Library on the Oracle Technology Network (OTN) Web site: http://www.oracle.com/technology/documentation/epm.html Deployment-related documentation is also available on both Oracle Technology Network (OTN) and the Oracle E-Delivery Web site, which is: http://edelivery.oracle.com/EPD/WelcomePage/get_form Individual product guides are available for download on the Oracle Technology Network (OTN) Web site only.

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. Top of Document

Copyright 2010, Oracle and / or its affiliates. All rights reserved. http://www.oracle.com