Oracle Essbase Integration Services Release 9.3.3.0.00 Readme To view the most recent version of this Readme, see the 9.3.x documentation library on Oracle Technology Network (OTN) at http://www.oracle.com/technology/documentation/epm.html. [Skip Navigation Links] About This Release... 2 Release Type... 2 Supported Installation Paths... 2 Supported Platforms... 2 Supported Languages... 2 Release Compatibility... 2 Defects Fixed... 2 Defect Fixed in Release 9.3.3.0.00... 2 Defects Fixed in Release 9.3.1.5.00... 2 Defects Fixed in Release 9.3.1.4.00... 3 Defect Fixed in Release 9.3.1.3.01... 3 Defect Fixed in Release 9.3.1.2.01... 3 Defects Fixed in Release 9.3.1.2.00... 3 Known Issues in Release 9.3.3.0.00... 4 System Limitations... 6 Hybrid Analysis Limitations... 6 Installing Release 9.3.3.0.00... 8 Before Upgrading Essbase to Release 9.3.3... 8 Installation Procedure Overview... 8 Installation Notes... 9 Installing in Directories with Names that Contain Spaces... 9 Documentation Updates... 10 Documentation Versioning... 10 Required Third-Party Software Version References in Documentation... 10 Drill-Through Reports for Alternate Hierarchies... 10 1
About This Release This Readme file describes the defects fixed in Oracle Essbase Integration Services 9.3.3.0.00 as well as the necessary instructions for installing this release. Release Type This maintenance release is cumulative and incorporates all service fixes to the 9.3.1 release. This release requires a full re-install of Integration Services. Supported Installation Paths The supported installation path for Release 9.3.3 is from Release 9.3.1 and subsequent service fixes and packs only. Supported Platforms Information about system requirements for Release 9.3.3 products is available in the Hyperion Installation Start Here. See http://www.oracle.com/technology/documentation/epm.html. Supported Languages Release 9.3.3 is English only. Release Compatibility Release 9.3.3 is interoperable only with other Release 9.3.3 products. This means that you must upgrade all products in your environment to Release 9.3.3. Defects Fixed Defect Fixed in Release 9.3.3.0.00 Top of Document 9772175 Drill-Through Reports. Drill-through reports were copied in error after clicking No at the confirmation prompt. Defects Fixed in Release 9.3.1.5.00 8549471 OLAP Model. It takes much longer than expected to open an OLAP model. 6619590 Data Source. Integration Services checks access to all schemas while connecting to an Oracle data source. The correct behavior is to skip checking access. 8687435 Member Load. Member loads may terminate with an error stating there is incorrect syntax. 8597954 Data Load. An Integration Services data load into an ASO cube via a.cbs script fails to load any data, but Integration Services returns a status of successful. 2
Defects Fixed in Release 9.3.1.4.00 6586512 - OLAPISVR.LOG. Integration Server hangs when OLAPISVR.LOG reaches LOGFILEMAX setting size. 8304252 Data Load. An Integration Services data load into an ASO cube via a.cbs script fails to load any data, but Integration Services returns a status of successful. 8304235 Log File. Log file contains message Data load terminated with errors when data loads successfully. 7301275 Drill-Through. Integration Services stops when users run drill-through reports. 7714801 Security Privileges. Integration Services Console registry is not caching securityprivileges values. 7537168 - ODBC License. ODBC license error is generated when attempting to perform member and data loads concurrently when using the Delete and Restore Database option. Defect Fixed in Release 9.3.1.3.01 7646419 Drill-through. Integration Services stops unexpectedly when multiple users simultaneously run drill-through reports. Defect Fixed in Release 9.3.1.2.01 7721750 Data Load. An Integration Services data load into an ASO cube via a.cbs script fails to load any data, but Integration Services returns a status of successful. Defects Fixed in Release 9.3.1.2.00 6785621, 6872208 Drill-Through Reports. Specifying invalid filters to customize a drill-through report could cause Integration Server to hang. This would happen if users were allowed to customize the drill-through report, and they entered invalid filters in the Select Data Filters dialog box. 7170394, 6807257 Data Load. The maximum number of tables that users could set in ESS_MAX_TABLES had been set to 16. This caused data load failures with models having more than 16 physical tables. The maximum number of tables is now 108. 7170388, 6909600, 8-644601811 Fact Table. When users ran data loads from the Integration Services Console, a list of alternate fact tables was downloaded to provide the option of selecting a fact table. In large databases, this could take a significant amount of time. Now the list is not downloaded unless the user selects the Alternate Fact Table check box. 7212289, 7342177 Integration Server. When several batch jobs for data loads were run consecutively, and one or more scripts had empty parameters, Integration Services would sometimes shut down, forcing the user to manually restart the application. This condition has been corrected. 6889763, 6882477 Essbase Access. In some drill-through operations, Integration Services could not access Essbase in Shared Services mode. This condition has been corrected. 7138407 OLAP Metaoutlines. When building a cube in Integration Services Release 9.3.1., using a metaoutline that had been generated in Release 7.x, a false error condition sometimes prevented users from building the cube. The accompanying error message read: A shared member must be at the leaf level and cannot appear before its primary member. The condition now generates a warning message instead of an error, allowing the cube to be built. 3
7261546 Member Load. During loading operations, the condition of having a shared member not being at a leaf level, or appearing before its primary member, should generate a warning message and allow the load to continue. Instead, an error condition was incorrectly displayed even though the load completed successfully. 7319955, 7158311 Data Load. When users ran a member load and data load in the same job from Integration Services to build an aggregate storage (ASO) cube in Essbase, the data load sometimes failed and generated an error message stating, Data load buffer does not exist. The cube was built with the proper outline, but the data load would fail because the buffer would be unavailable. This condition has been corrected so that the data load completes successfully. 7360009, 7393959 Drill-through. If users changed passwords, sometimes drill-through report operations would fail because of encryption errors. 7414122 - Duplicate User-defined Members. When a duplicate user-defined member was added to a dimension, an invalidation error occurred and the metaoutline could not be saved. 7268275 Data Load. When the Default Miscellaneous Member option was enabled for the aggregate storage option, the default members were not added and the data load failed. The data load failure has been addressed; however, you may need to reload any rejected records. Known Issues in Release 9.3.3.0.00 The following issues are the noteworthy known issues of this release. Top of Document 7215847 Drill-Through Reports. If your metaoutline contains several chains of recursive hierarchies, you should create a separate drill-through report for each chain, otherwise the template SQL substitution will fail. 7475156 Data Load. Performing a member and data load in Integration Services sometimes causes the outline to lock in Essbase if the size of the host name is too large. This results in the member and data loads failing to complete. Workaround: Set NODENAME as short host name in the essbase.cfg file and restart Essbase Server. 7589430 Installation. The Windows x64 version of Integration Server uses Microsoft.NET files that are included with certain Microsoft products, such as SQL Server 2005 or Visual Studio 2005. Integration Server will not start as a service or from the executable/bat file if it cannot locate the necessary.net files. Workaround: Stop Integration Server. Download and install version 2.0 or later of Microsoft.NET from the Microsoft web site. You can also install the.net files using Windows Update. Then, restart Integration Server as a service or from the executable/bat file. 7831887 Shared Services. 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. 9092675 Metaoutlines. After upgrading from Integration Services 6.5.x to 9.3.1.3, some metaoutlines cannot be saved after the addition of a user-defined member. Workarounds: Use the 6.5.x version to edit metaoutlines and use 9.3.x version for daily operations, such as data loads. Export the metaoutline to XML and edit the XML file manually. 4
9845199 - Integration Services Console. When opening OLAP models or metaoutlines in the Integration Services Console, a server message, "Unable to get UTF-8 locale", may erroneously appear. 9847457 OLAP Metadata Catalog Setup. If all fields in the Create in the OLAP Metadata Catalog Setup dialog box are empty, and you click the Create button, a catalog will not be created, although, an error message will not appear. You must have filled in the fields correctly before clicking Create in order to create a new OLAP Metadata Catalog. When opening HTML documentation or HTML Help in Firefox 3.5.9 or later, or in Internet Explorer 8.0 or later, you may experience some display or navigational anomalies, including images not loading. This does not affect the integrity of the application content. Log file on UNIX. If you delete the log file while the Server is running on UNIX environment, you must stop and then restart the server to create a new log file. SQL driver on UNIX and Linux. During XML import/export operations, the SQL driver on UNIX and Linux platforms writes expiration code in the odbc.ini file. In 15 days, the user receives a connection error when attempting to perform an XML import or export operation. Note: This affects ODBC-JDBC bridge functionality only. The main ODBC connectivity continues to function normally. Workaround: Manually set the odbc.ini file to read-only using the command: chmod 444 odbc.ini 73905, 73906, 73910, and 74122 Naming conventions. Multibyte Character Set (MBCS) characters should not be used in the names of these entities: OLAP models Metaoutlines Data sources Owners Data Sources. If you run Essbase 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. WORKAROUND: Use OCI drivers. Time-based Incremental Load. 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. @ISUDA Function Validation. Although Essbase Administration Services validates @ISUDA functions, Integration Services may not. Oracle strongly recommends you use Essbase Administration Services to validate these functions. Japanese Encoding. If you use Japanese encoding, Hyperion recommends you use MS932 encoding instead of Shift-JIS. Drill-through. In order that drill-through operations function correctly in OLAP metaoutlines containing duplicate member names, you must fully identify a duplicate member by specifying all the ancestors for that member in Template SQL. Drill-through. If you customize drill-through reports at runtime and add a user-defined filter, keep the length of the filter under 8KB; otherwise, some members may not be included in the drillthrough report query. 5
Formulas. To verify member formulas, a user must have Create access to Essbase Server. Drill-through. 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. Drill-through. Drill-through operations are not supported on Unicode data. Data 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 Essbase. In such cases, be sure that the time dimension is built to span time periods of all fact tables. XML Import/Export. The import/export function is not available on 64-bit UNIX platforms. TBC Sample Application. 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 new executable name SQLCMD.EXE. WORKAROUND: Edit the batch file install_sqlsrv.bat located in the ISHOME\samples directory, where ISHOME is the directory where Integration Services is installed. Replace the name of the executable ISQL.EXE with the new executable name SQLCMD.EXE. Duplicate Member Names. If you use SQL override for outlines containing duplicate member names, the generated SQL may have a WHERE clause containing more columns than an outline containing unique member names. This is because Essbase Integration Services adds columns to outlines containing duplicate member names to give them a unique identifier. This may be an issue in data load operations using SQL override. System Limitations Integration Services supports full Unicode functionality only on Oracle relational database servers. We recommend you use the same language for your Data Source Names (ODBC 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. To retain and upgrade Dynamic Time Series settings made in Essbase Integration Services prior to Release 6.5.4, open and save the metaoutline using the current release. For recursive and alternate hierarchies, we recommend that you verify your settings. Integration Services does not support user-defined tables created in Sybase or Informix. Hybrid Analysis Limitations If you are using Hybrid Analysis and have either the OLAP Metadata Catalog or your data source in an Oracle database, you must use DataDirect drivers. Hybrid Analysis no longer supports Oracle Call Interface (OCI). Hybrid Analysis is not supported on Accounts dimensions that contain a user-defined member at level zero under the following conditions: there is no formula associated with the user-defined member, and any consolidation option except ~(ignore) is selected. Drill-through on Hybrid Analysis data with transformations is not supported. For ragged hierarchies in Hybrid Analysis, the Essbase level-0 members (those members from the Integration Services member set marked as "Build down to here") cannot be NULL. 6
Hybrid Analysis drill-through returns transformed values When performing a drill-through on Hybrid Analysis data with transformations, Essbase returns the transformed value instead of the database value associated with the member. This causes an incorrect SQL query formulation for drill-through reports associated with Hybrid levels that have transformations. Hybrid Analysis causes error when lock list is full Depending on the nature of the end user query, Hybrid Analysis may need to issue SQL queries to the relational database that access a large number of rows. If this happens on a DB2 database, the error "SQLCODE-912" may occur. This is caused when DB2 attempts a lock escalation unsuccessfully because the lock list is full. Please contact your relational database administrator to set the lock list to a more appropriate limit. Using DB2 on HP with the HAMAXQUERYTIME When using DB2 on an HP UNIX system, setting the HAMAXQUERYTIME option to 1 in essbase.cfg causes Essbase to terminate abnormally. Hybrid Analysis may not perform loads in Solaris On Solaris platforms, Hybrid Analysis may not perform loads because it is not able to populate the locale() even though ESSLANG is set properly. Hybrid Analysis Guidelines Hybrid Analysis supports data that is stored using either block storage or aggregate storage. Hybrid Analysis supports Unicode-enabled data sources. You can associate an attribute member with a member enabled for Hybrid Analysis but you must make the association by metaoutline member name and not by level. Hybrid Analysis does not return numeric data in a spreadsheet if the member from the Accounts dimension is part of a ragged hierarchy. Hybrid Analysis is not supported with the Member Selection feature. You cannot select Hybrid Analysis members from the Member Selection dialog box. If you have multiple levels of Hybrid Analysis members in your outline, performing a zoom out operation on the bottom level Hybrid Analysis member takes you directly to the Essbase parent member, bypassing all other Hybrid Analysis levels. You cannot apply properties of the Account Info tab to Hybrid Analysis members. Specifically, Time Balance, Skip, Variance Reporting, or Currency Conversion properties are not supported for Hybrid Analysis-enabled members. Hybrid Analysis supports Dynamic Time Series; however, if the time dimension contains hybridanalysis enabled members, the time dimension does not support Dynamic Time Series. You cannot apply properties of the Account Info tab to Hybrid Analysis members. Specifically, Time Balance, Skip, Variance Reporting, or Currency Conversion properties are not supported for Hybrid Analysis-enabled members. Top of Document 7
Installing Release 9.3.3.0.00 The section includes important information about installing this release Essbase Integration Services. Install Essbase Integration Services Release 9.3.3.0.00 by running the installation programs provided in this release. For information on running Essbase Integration Services installation programs, see the Hyperion Essbase Integration Services Release 9.3.1 Installation Guide for the platform you are using. Before Upgrading Integration Services to Release 9.3.3 HP-UX installations (Known Issue 9904406): When upgrading to Release 9.3.3 on the same HP-UX computer on which Release 9.3.1.x is installed, installation may fail due to file permission issues. To avoid these file permission issues, perform theses tasks before upgrading to Release 9.3.3: 1. Change directories to $HYPERION_HOME/common. 2. Enter this command: chmod R 750 JCE JDBC XML loggers 3. If Provider Services is installed, change directories to $HYPERION_HOME/AnalyticProviderServices/lib. 4. Enter this command: chmod 666 *.ico You can now upgrade Shared Services, Essbase, Essbase Administration Services, Provider Services, and Integration Services. Installation Procedure Overview This section provides an overview of the installation procedure. For detailed information on running Essbase Integration Services installation programs and configuring ODBC sources, see the Hyperion Essbase Integration Services Release 9.3.1 Installation Guide for the platform you are using. To install the 9.3.3.0.00 release: 1. Shut down Integration Services Console and Integration Server. 2. Download and extract the installation files to a local drive. 3. Run setup and complete the installation program. 4. If you are using DataDirect ODBC drivers: Configure the DSN for your OLAP Metadata Catalog to point to the latest DataDirect driver. Configure the DSNs for your data sources to point to the latest DataDirect drivers. 5. Start Integration Server. 6. Test connectivity by starting Integration Services Console and connecting to your OLAP Metadata Catalog and a data source. 8
Installation Notes Hyperion Installation Start Here The Hyperion Installation Start Here helps you plan your Hyperion System 9 installation and configuration. This document should be read first and used in conjunction with the procedures for installation, configuration, and post-configuration provided in the individual installation guides. The Hyperion Installation Start Here provides information about system requirements, prerequisites, default ports, release compatibility, recommended installation sequence and startup dependencies, and other information to help you plan your product installation and configuration. Supported ODBC Drivers and Other Connections Essbase Integration Server manages connections to the relational data source and to the OLAP Metadata Catalog. A current list of supported Open Database Connectivity (ODBC) drivers and Java Database Connectivity (JDBC) drivers is provided in the Hyperion Installation Start Here. Note: Use the Hyperion Installation Start Here for the latest in third-party platform and software version support information. In the 9.3.1 Integration Services documentation, some references to version numbers of third-party software may no longer be valid. ODBC Notes "Localhost" is not a valid server name. In the Login dialog box, you must specify a machine name or machine IP address in both the Essbase Integration Server frame and the Essbase Server frame. For UNIX systems, the Integration Services installation creates a template odbc.ini. To store information about Open Database Connectivity (ODBC) connections from Integration Server to the OLAP Metadata Catalog and relational data sources, edit this file using your preferred editor. To configure a Teradata data source, an environment variable, TDODBC, must be set manually. Configuration File Entry for DB2 OS/390: 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] Installing in Directories with Names that Contain Spaces On Windows systems, Oracle recommends that you install Oracle s Hyperion products in directories with names that do not contain spaces. If, however, your company policy requires that you install a Hyperion product in a directory whose name includes spaces, such as C:\Program Files, you must use the short name (or 8.3 alias) for all references to the installation directory. For Essbase Integration Services, this includes directory references in these environment variables: HYPERION_HOME ISLOADINFO ISHOME 9
The short name consists of the first six characters of the directory name, followed by a tilde (~), and a unique, incrementing number. On Windows, you can view directory short names by entering dir /x at the command line. For example, if you installed Essbase Integration Services in C:\Program Files\Hyperion\eis, the short name for the ISHOME variable might be: C:\Progra~1\Hyperion\eis Documentation Updates Documentation Versioning Top of Document All documentation associated with this release (Installation Guide, System Administrator s Guide, Data Preparation Guide, OLAP Model DTD and OLAP Metaoutline DTD) is labeled as release 9.3.1. Required Third-Party Software Version References in Documentation In the 9.3.1 Integration Services documentation, some references to version numbers of third-party software may no longer be valid. Refer to the Hyperion Installation Start Here for the latest information on supported third-party software versions. Drill-Through Reports for Alternate Hierarchies 9202673 When working with drill-through reports for alternate hierarchies, you must create a separate drill-through report for each hierarchy. Top of Document Copyright 2010, Oracle and/or its affiliates. All rights reserved. http://www.oracle.com 10