About This Service Fix... 1 New Features... 1 Defects Fixed... 1 Known Issues in Release Documentation Updates... 6

Transcription

1 Oracle Essbase Integration Services Release Readme [Skip Navigation Links] About This Service Fix... 1 New Features... 1 Defects Fixed... 1 Known Issues in Release Documentation Updates... 6 About This Service Fix This Readme file describes the defects fixed in Oracle Essbase Integration Services Service Pack as well as the known issues in this release. New Features Certification Matrix 1 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, posted at System requirements are no longer part of the Oracle Hyperion Enterprise Performance Management System Installation Start Here. Supported Languages 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 Defects Fixed Defects Fixed in Release Member load. In the batch file created for EIS scheduling for member loads, the path was not updated to include the start command. ( ) Console. Creating the fact table by selecting the Menu > Tools option failed. ( )

2 Data load. Batch file executed during data loads falsely reported that load was terminated with errors despite data load being successful. ( , , ) Console. Integration Services Console was not granting re-access to users after they exited the application because user ID information was not being cached. ( , ) Data and member loads. Data and member loads failed when run from a.cbs script, but Integration Services status indicated the load was successful. ( , , ) Defects Fixed in Release These defects are fixed in Integration Services release The defect number follows the description of the defect. Drill-Through Template SQL. Incorrect table alias names were generated in the SQL query created by Integration Server. ( , ) Drill-Through Template SQL. Integration Server terminated abnormally when verifying Drill-Through Template SQL. ( ) 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. ( , ) Defects Fixed in Release These defects are fixed in Integration Services release The defect number follows the description of the defect. Console. When building a cube in Integration Services Release , using a metaoutline that been generated in Release 7.x, a false error condition sometimes prevented users from building the cube. ( ) Console. 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 a manual restart. ( ) Load. In data loads, the displayed total of records loaded and records rejected exceeded the number of records in the outline. ( , ) Drill-Through. If users changed passwords, sometimes drill-through report operations would fail because of encryption errors. ( , ) 2

3 Known Issues in Release The following issues are the noteworthy known issues of this release. ODBC Notes 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. 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] JISX0213 Japanese Character Set Not Supported 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. ( , ) Windows Server 2003 SP1 May Experience Abnormal Shutdown 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: Column Names with 0x5C Double-byte Characters May Not Display If column names contain 0x5C double-byte characters, the columns may not display in a table. ( , 2-HYPER ) MBCS Characters Should Not Be Used in Names of Some Entities Multibyte-character-set characters should not be used in the names of these entities: OLAP models Metaoutlines Data sources Owners ( ; 2-HYPER , 73905, 73906, 73910, and 74122) 3

4 Oracle Database as Unicode Data Source 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. Time-based Incremental Load Limitation 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. Unable to Functions 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. Japanese Encoding If you use Japanese encoding, Oracle recommends you use MS932 encoding instead of Shift-JIS. Specifying Ancestors in Template SQL for Drill-Through Operations on Duplicate Members In general, Oracle does not recommend using Drill-Template SQL for OLAP metaoutlines that support duplicate member names. If you still choose to use Drill-Through Template SQL for OLAP metaoutlines that support duplicate member names, Oracle suggests you take the following actions in order for Drill-Through Template SQL to function correctly: Associate database keys for the drill-through-enabled members. To do this, in the General tab of the Member Properties dialog box for each drill-through-enabled member, in the Member Key Column drop-down list, select the appropriate database key columns for the drill-through-enabled members. These actions are valid for drill-through reports defined on any member level, including level zero members. For drill-through defined on level zero members (leaf nodes), you can also fully identify a duplicate member by specifying all the ancestors for that member in Template SQL. In the following example of Template SQL using the TBC sample, for a drill-through intersection defined on Product.SKU, a WHERE clause was added (see bolded text) for the ancestor of SKU in order to fully define the member: SELECT DISTINCT ac."sku", ac."sku_alias", ac."caffeinated", ac."ounces", ac."pkgtype", ac."introdate", aa."supplierid", ad."supplier_alias", ad."address", ad."city", ad."state", ad."zip", ad."country" FROM TBC.SALES aa, TBC.PRODUCTDIM ab, TBC.PRODUCT ac, TBC.SUPPLIER ad WHERE aa."productid" = ac."productid" AND aa."supplierid" = ad."supplierid" 4

5 AND ac."sku" = ab."sku" AND ((($$Year-COLUMN$$ IN ( $$Year-VALUE$$)))) AND (ab."family" in ('100')) AND (((ab."family" in ('100','200','300','400','Diet')) AND ($$Product-COLUMN$$ IN ( $$Product-VALUE$$)))) The caveat to the solution given in the above example is that the member is fully defined only for children of Product 100; it is not practical to define Template SQL for every possible ancestor value. ( , 1-156SS6) Runtime Filter Condition Limitation for Customized Drill-Through Operations 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. (1-147T5F) Users Without Create Access to Essbase Server Cannot Verify Member Formulas To verify member formulas, users must have Create access to the Essbase Server. ( ) Updating Drill-Through Reports Not Supported for Outlines Containing Duplicate Member Names Release 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 Operations Are Not Supported on Unicode Data in Release Records Rejected During Data Load when Alternate Fact Table Selected 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. ( ) SQL Server 2005 Requires Name of New Executable in Sample Creation Scripts to Create TBC Sample Tables and to Load Sample Data 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 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. ( ) Application Naming Restrictions When managing Oracle s Hyperion Shared Services models and naming applications, you cannot use the forward slash (/), backslash (\), or double quotation ( ) characters. ( ) 5

6 Read-only Permission to External Data Sources for Drill-Through Reports Oracle recommends that your users be granted read-only permission to external data sources for drillthrough reports and custom data load SQL. Adding Alternate Hierarchy a Second Time Duplicates Values 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 > and 100 > WORKAROUND: Use user-defined SQL to edit data load commands. ( ) Start and Stop Controls for Windows Service on Windows 2003 SP1 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. ( ) Long Table and Column Names Truncated in the Drill-Through Wizard 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. ( ) 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 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 Integration Services prior to release 6.5.4, open and save the metaoutline using 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. Documentation Updates Accessing Hyperion Product Documentation The most recent version of each Hyperion product guide is available for download from the Documentation area of the Oracle Technology Network (OTN) Web site ( Deployment-related documentation is also available 6

7 from the Oracle E-Delivery Web site ( Individual product guides are available for download on the Oracle Technology Network (OTN) Web site only. Note: Not all of the documentation for this product has been updated from Release or Similarly, the product UI may not have been updated from Release or 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. Copyright 2009, Oracle and/or its affiliates. All rights reserved. 7