For information on Essbase Studio features in this release, see the Oracle Essbase Studio New Features guide.

Transcription

1 Oracle Essbase Studio Release Readme [Skip Navigation Links] Purpose...1 New Features...1 Translation Support...1 Installation Information...2 Known Issues...2 Defects Fixed in This Release...10 Tips and Troubleshooting...11 Documentation Updates...14 Accessibility...22 Purpose This document includes important, late-breaking information about this release of Oracle Essbase Studio. Review this Readme thoroughly before installing Essbase Studio. It is our goal to Oracle products, services, and supporting documentation accessible to the disabled community. Oracle Hyperion Enterprise Performance Management System supports accessibility features, which are described in Appendix A of the Oracle Essbase Studio User s Guide and Oracle Essbase Studio Online Help. This readme file is accessible in this release in HTML format. New Features For information on Essbase Studio features in this release, see the Oracle Essbase Studio New Features guide. Translation Support Top of Document Top of Document 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 Top of Document 1

2 Installation Information 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. EPM System Changes 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. 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. ODBC Requirement for MySQL If you plan to use a MySQL database as a data source: For MySQL Enterprise version, the appropriate DataDirect ODBC drivers are installed automatically with the Essbase installation. For MySQL Community version, you must obtain the appropriate ODBC drivers directly from MySQL. Known Issues The following issues are the noteworthy known issues of this release. General Issues Top of Document Defect Number N/A Known Issues Oracle Essbase Spreadsheet Add-in for Excel works in native locale. If Spreadsheet Addin does not receive data in native locale, drill-through on cubes built in Essbase Studio is not supported. 2

3 Defect Number Known Issues N/A Transformation rules defined in the Essbase model will not be used in query generation for drill-through operations The JISX0213 Japanese character set, which replaces the JISX0208 and JISX0212 Japanese character sets, is supported on Windows Vista. The Essbase family of products does not support the JISX0213 Japanese character set Individual file names in a text file data source must not contain spaces If a name too long error is returned when attempting to deploy a cube, add an entry for the server.tempdir property to the server.properties file, and specify a shorter directory path. For example: server.tempdir=c:\\studiotemp When using Hyperion Smart View or Essbase Spreadsheet Add-in to query cubes built in Essbase Studio, if the intersection for a drill-through cell is represented by both a base member and one or more associated attribute members, you cannot perform drillthrough on that cell. Specifically, drill-through will not work on an intersection (cell) that is represented by members of a base dimension and members of attribute dimensions. When specifying intersections for a drill-through report in Essbase Studio, do not specify both the base and attribute hierarchies from a multichain hierarchy. Select only one of the hierarchies for drill-through. If you require drill-through from an intersection containing a base member and attribute members, you must build the cube using Essbase Integration Services A 255-character limit applies to certain objects that you name in Essbase Studio. These objects are: Data source connection names User-defined table names Metadata element names, such as dimension elements and hierarchies Alias sets Cube schema names Drill-through report names Note: These are the limits on Essbase application and database names: 8-bytes for non-unicode 30-characters for Unicode 3

4 Defect Number Known Issues If a change is made to hierarchy that is already used in an Essbase model, that change is not automatically carried over to the Essbase model. For example, if a leaf level member is removed from a hierarchy, that change is not automatically reflected in any Essbase models in which that hierarchy participates. However, any affected cube schemas are automatically updated. Workaround: Open the related cube schema and overwrite the existing Essbase model. Note: Changes can be made to certain metadata elements which do not require you to overwrite an existing an Essbase model. See Essbase Model Design Improvements in the Oracle Essbase Studio New Features guide for a complete listing When deploying a cube for the first time, and the cube contains text or date measures, the data is loaded correctly. Upon subsequent deployments of the cube, selecting the Load data option along with either the Add to existing data or Subtract from existing data 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 When migrating an OLAP metaoutline from Essbase Integration Services to Essbase Studio, members in a hierarchy may not be sorted properly in the deployed Essbase cube if both transformation and sorting rules are defined on the original Integration Services member set. In Essbase Studio, performing transformation in Essbase Model Properties does not resolve the issue. Workaround: Perform transformation in the Dimension Element Properties dialog box by editing the key binding expression of the dimension elements Microsoft Windows authentication is not supported for data source connections to Microsoft SQL Server. (Duplicate defect number: ) In Essbase cubes that support duplicate member names, drill-through fails when performed on a member where the key binding is different from the caption binding. Workaround: Create drill-through reports based on Essbase cubes that support unique member names only Re-importing the catalog fails when the catalog was cleared by deleting objects in the Essbase Studio Console. Workaround: In the console, clear the catalog by deleting objects as follows: Metadata elements from the Metadata Navigator Data source connections from the Data Sources tab of the Source Navigator Minischemas from the Minischemas tab of the Source Navigator Alias sets from the Alias Set Manager Then, perform the re-import. 4

5 Defect Number Known Issues When using the MaxL Deploy command, cube redeployment fails in incremental update mode if more than 100 rules are generated for a non-unicode mode application. Workaround: When redeploying, use the default full deployment mode instead of performing an incremental update. The example below provides the same behavior as a Deploy command that uses the incremental_load and update all parameters: deploy outline from model 'MYModel' login 'admin' identified by 'password' on host 'MYSERVER' to application 'MYAPP' database 'MYDB' using connection 'MYCONNECTION' on error write 'MYModel.err'; This example deletes existing members before deployment: deploy outline from model 'MYModel' with option delete_members login 'admin' identified by 'password' on host 'MYSERVER' to application 'MYAPP' database 'MYDB' using connection 'MYCONNECTION' on error write 'mymodel.err'; This example deletes the existing Essbase database before deployment: deploy outline from model 'MYModel' with option delete_database login 'admin' identified by 'password' on host 'MYSERVER' to application 'MYAPP' database 'MYDB' using connection 'MYCONNECTION' on error write 'MYMODEL.err'; When deploying cubes that contain varying attribute associations, selecting an incremental load option (update or rebuild) causes the deployment to fail. Workaround: Instead of performing an incremental load, use Essbase Administration Services Console to open the affected outline and delete the varying attribute dimension. Then perform a full deployment from Essbase Studio Console to the existing cube in order to update the varying attribute association The labeling rules listed in the Editing Labeling Rules dialog box were not translated and appear in English for all languages. The Editing Labeling Rules dialog box is accessed from the Time Depth area of the Calendar Hierarchy dialog box, as described in Defining Time Depth in the Oracle Essbase Studio User s Guide Varying attributes do not support NULL values in the FROM or TO columns of the history table. When working with varying attributes, if the history table contains rows with a NULL value in either the FROM or TO columns, then the attribute values from these rows are not built into an attribute dimension. Workaround: Ensure that there are non-null values in the FROM and TO columns of the history table. For more information on history tables, see Working with Varying Attributes: Setting Up a History Table. 5

6 Defect Number Known Issues If two independent dimensions have the same leaf member name for one varying attribute, deployment fails with the error, Duplicate name of the field in the query. For example, suppose there is a varying attribute dimension, VAYRPER, and two independent dimensions, Period and Year. If the leaf member name is the same for both Period and Year in the Essbase Model Properties, Independent Dimension Binding dialog box, the deployment will fail. Workaround: Rename the column for the physical relational table that will be used for the leaf member name. If that is not possible, you can create a user-defined table with the different column name and build the second independent dimension based on a column in the user-defined table When running Essbase Studio Server in nonstreaming mode (server.essbase.streamingcubebuilding=false), deployment fails when the Essbase model is based on a Unicode data source. Workarounds: Use streaming mode (server.essbase.streamingcubebuilding=true). Use nonstreaming mode (server.essbase.streamingcubebuilding=false). Create a DSN and enable the N-CHAR support option as follows: On Windows, use the ODBC Data Source Administrator to create a DSN with the Enable N-CHAR Support option selected. This option is found on the Advanced tab of the ODBC driver setup dialog box. On UNIX or Linux, edit the odbc.ini file to create a new DSN, and set the EnableNcharSupport value as follows: EnableNcharSupport=1 In the Cube Deployment Wizard, select the ODBC (Enter ODBC DSN Name) option and provide the DSN name you created. See the Essbase Studio User s Guide for information on setting the server.essbase.streamingcubebuilding property In minischemas based on MySQL data sources, you cannot add joins manually (that is, using the mouse to drag a join line) between a user-defined table and a source table when the two columns to be joined are both of type int (integer). You can add joins manually between a user-defined table and a source table when the two columns to be joined are both non-integer type columns, such as varchar or datetime. Workaround: For joins between user-defined tables and source tables, to add joins between columns of type int, use the main menu (Schema, then Add Join) or rightclick menu (Add Joins). 6

7 Defect Number Known Issues Deploying From Text File Data Sources Cube deployment from text file data sources is always done in nonstreaming mode, regardless of how the server property, server.essbase.streamingcubebuilding, is set. Essbase Studio Server uses the nonstreaming cube building method automatically for text file data sources; you will not be asked about or notified of this internal load method. Cube deployment progress statistics are not supported on text file data sources When creating aliases by inspection, note that the search criteria you enter in the Pattern for alias columns text box is case-sensitive. For example, if alias columns in your data source are suffixed with the pattern, _ALIAS, uppercase, then you must enter *_ALIAS in order to locate those columns When creating aliases by inspection, the list of data source connections from which you can choose includes all existing connections. However, you can only select connections to relational sources and text file sources. Any other selections are invalid In Smart View, when performing drill-through from an Essbase Studio-sourced cube to FDM, if the EPM System Single Sign-On token expires before the sessions of all products involved expire (Workspace, Analytic Provider Services, Essbase, Essbase Studio, FDM), the following message is displayed: Error: An error occurred logging on to the system using single sign-on. Please contact your administrator. Error: You do not have access to the application! , , Workaround: Log in again to Workspace from Smart View client. When working with recursive hierarchy drill-through, if you specify drill-through by generation, the drill-through report is not populated. Workaround: Specify drill-through intersections by levels, not by generations. When working with recursive hierarchy drill-through, if you specify drill-through by level and provide a level number, users are able to drill-through on all levels, not only the one you specified On Windows, when Essbase is started using OPMN, cube deployment fails for cubes built from Oracle Business Intelligence (OBI) data sources if the option ODBC (Essbase dynamically creates ODBC connection string) is selected in the Cube Deployment Wizard. Workaround: Start Essbase Studio Server in streaming mode, then perform the deployment. In streaming mode, the server.essbase.streamingcubebuilding property is set to true. See server.essbase.streamingcubebuilding in the Essbase Studio User s Guide for information on this property. Note: Localized versions of the readme may contain a second workaround which suggests using an ODBC DSN during deployment. This workaround is not valid and should be ignored. 7

8 Defect Number Known Issues Solaris only: Your machine likely has a network configuration problem if Essbase Studio Server fails to start, and either of the following messages appears in the server log file: , Cannot register server in catalog. Network error prevented server registration check. Workaround: Manually add a single, empty row to the Essbase Studio catalog database table, cp_server_key. Windows and AIX only: Cube deployment fails when you specify an Oracle OCI connect identifier in the Data source settings group of Cube Deployment Wizard. Windows Workaround: Replace the installed OCI DLLs with the correct files. Complete the following procedure to download and install the correct DLLs. 1. Download the Oracle Instant Client ZIP file (instantclient-basic-win zip) from the following URL and unzip the file: This ZIP contains all files required to run OCI, OCCI, and JDBC-OCI applications. Note: If the above link does not work, then perform a search on the Oracle Technology Network site to locate the file. 2. Copy all o*.dll files from this unzipped folder to the %EPM_ORACLE_HOME%\bin directory. 3. Restart Essbase Server. 4. Run the cube deployment from Essbase Studio using the OCI connection string. AIX Workaround: Copy the libocci.so file from $MW_ORACLE_HOME/ohs/lib to $EPM_ORACLE_HOME/lib, and then restart Essbase Server During cube deployment, if the Essbase model that is being deployed or its underlying data source contains MBCS (Multibyte Character Set) characters, the OCI data source setting option is not supported. Workarounds: Use streaming mode (server.essbase.streamingcubebuilding=true). Use nonstreaming mode (server.essbase.streamingcubebuilding=false). Create a DSN and enable the N-CHAR support option as follows: On Windows, use the ODBC Data Source Administrator to create a DSN with the Enable N-CHAR Support option selected. This option is found on the Advanced tab of the ODBC driver setup dialog box. On UNIX or Linux, edit the odbc.ini file to create a new DSN, and set the EnableNcharSupport value as follows: EnableNcharSupport=1 In the Cube Deployment Wizard, select the ODBC (Enter ODBC DSN Name) option and provide the DSN name you created. See the Essbase Studio User s Guide for information on setting the server.essbase.streamingcubebuilding property. 8

9 Defect Number Known Issues When creating a native (non-unicode) Essbase application from a Multibyte Character Set (MBCS) data source in streaming mode, an Essbase API limitation of bytes for character strings causes the cube deployment to fail. Workarounds: Run Essbase Studio Server in streaming mode (server.essbase.streamingcubebuilding=true); then, access the Essbase Model Properties page for the model and, in the General tab, enable the "Use Unicode character set" option. Then redeploy the cube. If there is no calendar hierarchy included in the Essbase model, run Essbase Studio Server in nonstreaming mode (server.essbase.streamingcubebuilding=false), then deploy the cube. For information on streaming and nonstreaming mode, see the server.essbase.streamingcubebuilding topic in the Essbase Studio User s Guide After installing and configuring release of Essbase Studio, two server.properties files appear in the installation, as described below. Be sure to use the correct file if you are adding or editing server properties. Oracle/Middleware/user_projects/epmsystem1/BPMS/bpms1/ bin/server.properties This is the valid server properties file. It contains the settings created by the EPM System Configurator during configuration. Use the file in this location when you are adding, removing, or modifying server properties. Oracle/Middleware/EPMSystem11R1/products/Essbase/EssbaseStudio/ Server/server.properties This server properties file is empty and is used by the Configurator as a template in creating the valid server.properties. Do not use this file Rules files for dimension builds created by Essbase Studio cannot be opened in Essbase Administration Services. XOLAP Issues Defect Number Known Issues N/A XOLAP does not support models based on multiple data sources You cannot deploy an XOLAP-enabled Essbase model that is based on an OBI data source XOLAP does not support models using hierarchies from user-defined tables. Top of Document 9

10 Defects Fixed in This Release Defect Number Defects Fixed In This Release Essbase Studio now correctly builds multichain hierarchies where two chains contain identical member names appearing in the same order, but the members come from different tables or different data sources Microsoft SQL Server database names that start with a number were not supported prior to this release. For example, the database names, 12studiocat or 321salesdata, were not supported An error occurred when attempting to open a saved relational-type drill-through report after changing the data source connection name on which it was based After deployment of aggregate storage-enabled models in Essbase Studio (or Essbase ASO-enabled applications in EPM Architect), the hierarchy settings and data storage type were not correctly reflected in the subsequent Essbase outline Data load from a text file data source was not working when the outline was built from an EPM Architect data source If you remove a member from a measure hierarchy, and the same measure hierarchy exists in the Context tab of a drill-through report, the change made to the measure hierarchy is correctly reflected in the drill-through report definition when next opened in the drill-through report editor In the Essbase Properties dialog box, Member Formula tab, the From External Source option was disabled, and was enabled only after applying changes, then saving, closing, and reopening the dialog box When deploying a block storage-type Essbase model based on a Dimension server data source (EPM Architect), the Expense Reporting properties were not being sent to Essbase Renaming alias sets was not working correctly and renamed alias sets were not properly reflected in the Essbase models in which they were being used Essbase model validation was not being performed on custom prefixes in the Alias tab, causing errors during cube deployment When the Essbase model was set to aggregate storage, options on the Info tab were enabled in error on the parent level of parent-child hierarchies, causing incorrect aggregations in the resulting outline. In the case of parent-child hierarchies, the options on the Info tab must only be enabled on the child level After deployment of an aggregate storage-type Essbase model that supports duplicate member names and contains a parent-child hierarchy, shared members were not created Essbase models containing calendar hierarchies were allowed to be created as block storage models in error. Now, when a cube schema contains a calendar hierarchy, the aggregate storage option in the subsequent Essbase model is automatically selected and cannot be cleared When loading varying attributes, if Essbase encountered an unknown value (that is, a value that does not exist in the dimension) in the column that is mapped to either the From or the To field, Essbase failed. 10

11 Defect Number Defects Fixed In This Release The English version of the Essbase Model page of the Preferences dialog box was displayed for all languages. The localized version was not displayed for any supported language Drill-through to an Oracle BI EE URL did not work for member names containing spaces (multi-word member names) In the Connection Wizard, the default port number was not properly restored upon reselection if it had previously been cleared and a different port number was input The Properties option is now disabled when the Root node (or folder) in the Metadata Navigator is selected. Note that the Root folder is not editable In the Cube Schema Wizard, the Preview All hierarchy s functionality was not correctly displaying all hierarchy members Essbase Integration Services catalog migration failed when the catalog data source to migrate to was a Microsoft SQL Server database When concatenating the MonthShortName function by, for example, appending an underscore character to the end of the expression, extra spaces and garbage characters were added to the end of the strings displayed in the sample data When attempting to perform a data load from multiple flat files (which is not supported), the load was unsuccessful, however, no error message or other indication of this was provided During configuration, when an Oracle Service Name was provided for the Essbase Studio catalog, the syntax for the catalog.url property was not properly formed in the server.properties file, and Essbase Studio Server then failed to start Any left outer joins created would disappear after closing and reopening the minischema Joins created in Japanese versions of Essbase Studio were not properly displayed after closing and reopening the minischema The MaxL deploy command was not working when issued from a MaxL Shell running on the 64-bit version of IBM AIX Member names were being truncated at 34 characters, even though 80 characters is the limit. Tips and Troubleshooting Limitations and Guidelines Top of Document The Essbase Studio User s Guide (PDF format) and the Essbase Studio Online Help (HTML format) contain an appendix entitled Essbase Studio Limitations and Guidelines, which describes various limitations you may encounter while working with Essbase Studio. Also, refer to the Known Issues section of this document for the latest information on limitations and guidelines. 11

12 One Studio Server per Catalog Database The Essbase Studio catalog database should not be used by two or more Essbase Studio Server instances, either simultaneously or in succession. Oracle strongly recommends that each Essbase Studio Server point to its own unique catalog database. Verifying Catalog URL Property Syntax If Essbase Studio Server fails to start, check the catalog.url property in the server.properties file to verify that the syntax is correct. If the syntax is incorrect, Essbase Studio Server will not start. If the syntax is incorrect, edit the catalog.url property to correct the problem. Then restart Essbase Studio Server. See the topic, catalog.url in the Essbase Studio User s Guide for more information and examples. Note: The server.properties file is located in: Oracle/Middleware/user_projects/epmsystem1/BPMS/bpms1/bin/server.properties Using the MaxL Import Dimensions Statement with Essbase Studio Rules Files ( , ) You can use the MaxL Deploy statement to load members and data into Essbase from a rules file that was created in Essbase Studio. The Deploy statement provides you with the simplest way to accomplish this task. You may, however, choose to use the MaxL Import Dimensions statement to load members from an Essbase Studio rules file. If you choose to use the Import Dimensions statement to build an outline, note that a problem exists when building an Accounts dimension either from the fact table or from a hierarchy containing only user-defined members. When this is 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 Import Dimensions 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'; Port Number Limitations for Drill-through ( , ) Two ports are used by Essbase Studio Server to communicate with Essbase Spreadsheet Add-in and Hyperion Smart View. These are transport.port and server.httpport. Changes to either of these port numbers will affect drill-through operations as described in the following sections. Changing the Transport Port Number After initial configuration using the EPM System Configurator, if the transport.port property in the server.properties file is changed manually, the following is the state of drill-through connectivity on cubes built prior to the port adjustment. In Hyperion Smart View, drill-through will not work properly. You must refresh the port number stored in the cube by following the instructions in Updating Cube Linkage. See the Essbase Studio User s Guide. Note: Cubes built after the port adjustment will work properly. In Essbase Spreadsheet Add-in, drill-through will work properly. 12

13 Changing the HTTP Port Number If you add an entry for the server.httpport property in the server.properties file to change it from the default setting of 9080, the following is the state of drill-through connectivity on cubes built prior to the port adjustment. In Essbase Spreadsheet Add-in, drill-through will not work properly. In order to use drillthrough with Essbase Spreadsheet Add-in on cubes built prior to the port adjustment, you must redeploy those cubes. Note: Cubes built after the port adjustment will work properly. In Smart View, drill-through will work properly. Problem Exporting Large Catalog Databases ( , ) Export fails without any specific error when exporting a large Essbase Studio catalog database. If your catalog database is large, perform the following procedure: 1. Create a file called EssbaseStudio.ini in the same location as EssbaseStudio.exe. 2. Add these lines to the file: -vmargs -Xmx1024m 3. Start Essbase Studio Console. 4. In the Source Navigator, select the Minischema tab and delete all minischemas. Note: Be sure to delete any user-defined joins before deleting the minischemas. 5. Perform the catalog export again. TCP/IP Must Be Enabled In Microsoft SQL Server If you are using Microsoft SQL Server 2005 or 2008 as the Essbase Studio catalog database or as an external data source, you must enable TCP/IP. To enable TCP/IP: 1. From the Start menu, select Microsoft SQL Server (2005 or 2008), then Configuration Tools, and then SQL Server Configuration Manager. 2. In the SQL Server Configuration Manager, expand the SQL Server 2005 Network Configuration node, and then select Protocols for <Instance Name>. <Instance Name> is the name of the instance of Microsoft SQL being used. 3. In the Protocol Name list in the right frame, right-click TCP/IP and then click Enable. The status in the right frame of the will display as Enabled. 4. Right-click the Protocols for <Instance Name> again, in the left frame, and then click Restart. 13

14 Oracle Advanced Security If you are using an Oracle database with Essbase Studio, you may want to configure the associated Oracle JDBC drivers with Oracle Advanced Security. Click the following link for information on Oracle Advanced Security: Documentation Updates Top of Document This section describes additional items, updates, and deletions that are not yet included in the Release documentation. 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): 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 from the Oracle E-Delivery Web site ( 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. Erroneous References in Localized Documentation In the localized versions of the Oracle Essbase Studio User s Guide, users should ignore references to the Business Model option related to Oracle Business Intelligence, Enterprise Edition. This functionality is not yet available in Essbase Studio in any language. Note on Deleting Tables from Data Source Connections If you want to delete all tables from a data source connection, Oracle recommends deleting the data source connection and creating a new connection. 14

15 Migrating Recursive Hierarchy Drill-through Reports from Integration Services Starting with release , Essbase Studio supports drill-through on recursive hierarchies. Therefore, the following guideline, listed in the Oracle Essbase Studio User s Guide, Integration Services Catalog Migration chapter, Guidelines for Metaoutlines and Models topic, is no longer valid: Metaoutlines that have drill-through defined on recursive hierarchies can be migrated, but recursive-hierarchy drill-through functionality is not supported in Essbase Studio. Accessibility Appendix Update The following items were not documented in the Accessibility appendix of the Essbase Studio User s Guide (PDF and HTML help formats): Additional Element on the Connection Wizard, Model Files page: Element Name Edit Column Properties button (launches the Column Properties dialog box) Equivalent Alt+E All new Column Properties dialog box: Element Name Name Data type Back Next Equivalent Alt+M Alt+D, then use the arrow keys to select an option: Text Integer Large integer Decimal Alt+B (previous column in selected table_ Alt+N (next column in selected table) Only Self Joins for OBI EE Data Sources ( ) When working with an Oracle Business Intelligence, Enterprise Edition data source, you may only create self joins (joins between columns in a single table). Drill-through Limitation Removed in Error ( ) The limitation on drill-through from a multi-cell range was inadvertently removed the Essbase Studio User s Guide. The following provides further clarification: With Essbase Studio-built cubes, drill-through on a range of cells is not available for Smart View or Essbase Spreadsheet Add-in. 15

16 Deploying Date Measures ( ) If you plan to deploy cubes that contain a date measure, keep in mind the following: Essbase Studio applies the MAX aggregation function to the date measure column when generating data load SQL so that the result set will come out to the last transaction date. In the following example, the Date column is used as a date measure. Product State Sales Date CA CA Using the MAX aggregation function, data is aggregated on the date, and Sales totals In the General tab of Essbase Model Properties, select a date format. The default date format is yyyy-mm-dd. In the Cube deployment options page of the Cube Deployment Wizard, be sure to select Overwrite existing data from the Load data options group. Removing Elements from a Minischema ( ) Data source connections retain information about user-defined joins in the following cases: When you delete a minischema that contains user-defined joins When you delete individual minischema tables that have user-defined joins going to or from them The join lines do not display after deletion; however, the data source retains information about any user-defined joins related to the deleted minischema or the removed table. This can adversely affect the SELECT statement created for cube deployment. When you want to remove a minischema or a minischema table that has user-defined joins, Oracle recommends that you always delete those joins first, then delete the minischema or minischema table. Note: Deleting a minischema does not delete the data source connection on which the minischema is based. Deleting tables from a minischema diagram does not remove those tables from the data source connection on which the minischema is based. Working with Varying Attributes: Setting Up a History Table ( ) When you work with varying attributes, you should prepare a table called the history table. The history table may contain a column (or more for outlines that support duplicate members) for varying attribute members, and several columns whose values can be used by Essbase to locate members in independent dimensions. 16

17 For example: Product Table ProductID Sku Other product columns Fact Table (can also be used to build Time dimension) ProductID Transdate Other fact table columns Product Package Table (history table for varying attributes [VA]) ProductID Pkg Type (VA) From Date To Date 1 Plastic Bag Jan Jul 1 Paper Bag Aug Dec The above example involves a fact table that contains the column Transdate, which can be used to build a Time dimension in Essbase Studio. However, most Essbase Studio users do not build a Time dimension from the fact table. In fact, Oracle recommends that users NOT build any dimensions directly from the fact table. Therefore, the table schema would look like this: Employee Table EmpID Emp Name SS# Time Table (to be used to build Time dimension) Columns for Date Time TimeID Fact Table (can also be used to build Time dimension) EmpID HireDate (TimeID) Other fact table columns Position Table (history table for varying attributes) EmpID Position (VA) From Date To Date The Position table has joins to the Employee and Time tables. The dimension build query for the Position dimension involves the Time table. Since it is much smaller than fact table, it should not have a major impact on build performance. If the To column is empty, the value of the From Date column can be the TimeID column. Position Table (the history table for varying attributes) EmpID Position (VA) From Date (TimeID) 17

18 Deployment Scenarios and Streaming Cube Building Property Considerations ( ) For cube deployment, Essbase Studio provides three data-retrieval mode options. Use of these modes depends on how you have set the streaming cube building property, server.essbase.streamingcubebuilding, as described below: Nonstreaming mode, with the connection string derived by Essbase Studio Server (the default) server.essbase.streamingcubebuilding=false In the Cube Deployment Wizard, select the option, ODBC (Essbase dynamically creates ODBC connection string). This option allows Essbase to conveniently establish connection to a data source during deployment and assumes default values for all connection attributes. In this case, Essbase Studio uses ODBC drivers during the deployment. Nonstreaming mode, with user-provided ODBC DSN server.essbase.streamingcubebuilding=false In the Cube Deployment Wizard, select the option, ODBC (Enter ODBC DSN name), and enter an ODBC DSN that you have previously set up. This option allows Essbase to take advantage of the attributes that have been specified in an ODBC DSN. For example, if the Essbase model you are deploying is based on a Unicode data source, you can create an ODBC DSN with N-CHAR Support enabled, and then specify this DSN at deployment time. Streaming mode, with the connection string derived by Essbase Studio Server server.essbase.streamingcubebuilding=true In the Cube Deployment Wizard, select the option, ODBC (Essbase dynamically creates ODBC connection string). This option allows Essbase to conveniently establish connection to a data source during deployment and assumes default values for all connection attributes. In this case, Essbase Studio uses JDBC drivers during the deployment. The following table provides guidelines on deployment modes and possible deployment scenarios. Deployment Mode Nonstreaming with connection string (default) server.essbase.streamingcubebuilding=false Deployment Scenario When the data source is relational, and you do not have any special requirements to adjust the default ODBC DSN connection attribute values. 18

19 Deployment Mode Nonstreaming with ODBC DSN server.essbase.streamingcubebuilding=false Streaming server.essbase.streamingcubebuilding=true Deployment Scenario When you want to change default values of connection attributes. The following are some examples: When an Essbase model is based on Unicode source database, "N-CHAR support" must be enabled. If you want to enable data compression to improve data transmission performance, Wire Protocol Mode can be set to 2. The authentication method of IBM DB2 connection is applied encryption options. On Windows, when Essbase is started using OPMN, for cubes built from Oracle Business Intelligence (OBI) data sources Essbase model is built from an EPM Architect data source Essbase model is built and deployed to Essbase from EPM Architect Cube schema contains a calendar hierarchy and data load mappings have been overridden Essbase model based on Unicode source database (N-CHAR support) Authentication Method of an IBM DB2 data source connection is an encryption option (Encrypt Password, Encrypt UserID and Password, or Client) On Windows, when Essbase is started using OPMN, for cubes built from Oracle Business Intelligence (OBI) data sources Starting Essbase Studio Server in the Foreground on UNIX ( ) The information in this section is an update to the section Starting Essbase Studio Server in the Foreground on UNIX, in the Essbase Studio User s Guide. By default, Essbase Studio Server runs in the background on UNIX. This behavior is controlled by a combination of one Essbase Studio Server property and four EPM System-created environment variables, and the startserver.sh file. The Essbase Studio Server property is server.runinbackground, and is set to true by default. 19

20 The environment variables are: EPM_ORACLE_HOME=<value> EPM_ORACLE_INSTANCE=<value> JAVA_HOME=$EPM_ORACLE_HOME/../jdk160_11/jre JAVA_OPTIONS=-DESSBASE_STUDIO_INSTANCE\=$EPM_ORACLE_INSTANCE/BPMS/bpms1 -DsuppressAPSProductInfo=<T F> You may choose to run Essbase Studio Server in the foreground. If so, you must edit the server property, the environment variables, and the startserver.sh shell file, as described in the following procedure. To run Essbase Studio Server in the foreground on UNIX, perform these steps: 1. In the Essbase Studio server.properties file, set server.runinbackground to false or comment it out. Note: The server.properties file is located in: Oracle/Middleware/user_projects/epmsystem1/BPMS/bpms1/bin/server.properties For more information on server.runinbackground, see the Essbase Studio User s Guide. 2. Set these variables in the environment where you will be running startserver.sh: EPM_ORACLE_INSTANCE=/<install path>/oracle/middleware/user_projects/epmsystem1 EPM_ORACLE_HOME=/<install path>/oracle/middleware/epmsystem11r1 JAVA_HOME="${EPM_ORACLE_HOME}/../jdk160_11/jre" JAVA_OPTIONS="-DESSBASE_STUDIO_INSTANCE=${EPM_ORACLE_INSTANCE}/BPMS/bpms1 -DsuppressAPSProductInfo=true" 3. Edit the Essbase Studio startserver.sh shell as follows. Note: The startserver.sh file is located in $EPM_ORACLE_HOME/products/Essbase/EssbaseStudio/Server/startServer.sh. a. Locate the last line of the file: nohup "${JAVA_HOME}/bin/java" -Xms128m -Xmx768m $JAVA_OPTIONS jar "${EPM_ORACLE_HOME}/products/Essbase/EssbaseStudio/Server/server.jar" >/dev/null & b. Remove nohup from the beginning of the line, the STDOUT to null direction (>/dev/null), and the background processing command (&) from the line; for example: "${JAVA_HOME}/bin/java" -Xms128m -Xmx768m $JAVA_OPTIONS -jar "${EPM_ORACLE_HOME} /products/essbase/essbasestudio/server/server.jar" 4. Start Essbase Studio Server by running the following statement:./startserver.sh 20

21 Update to Sample FDM URL Template Topic The FDM URL syntax has changed in this release. Therefore, the sample FDM URL template provided in the Context tab of the drill-through report editor has changed. The information presented here is an update to the Sample FDM URL Template topic in the Essbase Studio User s Guide. The URL syntax below assumes that the Product and Market dimensions were selected in the Context tab of the drill-through report editor and that these two dimensions are the only visible dimensions in the target FDM report. Syntax fdmappname=<app-name>&fdmtargetappname=<target-app-name>&attribute=system.ds.essbase &attribute=server.ds.<server-ds>&attribute=app.ds.<app-ds> &attribute=database.ds.<database.ds>&attribute=alias.ds.<alias-ds> &sso_token=$$css-token$$&attribute=product.id.$$product-value$$ &attribute=market.id.$$market-value&rcp_version=1.5.0 Parameters <server-name> The name or IP address of the server and the port to which you want to connect. <app-name> The FDM target application name. This value should match the FDM administratorassigned identifier given to the particular data set or repository within the product. For example, for the Comma sample application that ships with Oracle Hyperion Financial Management, Fusion Edition, the value would be comma. <target-app-name> The name of the Essbase application from which the drill-through request is originating. <server-ds> The name or IP address of Essbase Server that is hosting the Essbase application and database from which the drill-through request to FDM is originating. <app-ds> The name of the Essbase application from which the drill-through request is originating. <database.ds> The name of the Essbase database from which the drill-through request is originating. <alias-ds> The name of an alias table to use in the drill-through request. Use Default if you do not want to specify an alias table name. Product.id.$$Product-VALUE$$ The Point-Of-View (POV) dimension and the dimension member value, in this case, a value from the Product dimension. Essbase Studio automatically generates the dimension name as a part of the variable that is associated with the given dimension. Upon execution of the drill-through report, the name of the variable, $$Product-VALUE$$ will be substituted by the actual value from the POV; for example Cola. Example fdmappname=fdmapp&fdmtargetappname=sample&attribute=system.ds.essbase&attribute=server.ds.myfdmsvr11&attribute=app.ds.sample&attribute=database.ds.basic&attribute=alias.ds. Default&sso_token=$$CSS-TOKEN$$&attribute=Product.id.$$Product-VALUE$$ &attribute=market.id.$$market-value$$&rcp_version=

22 The following information is still valid and must be considered when creating your FDM URL syntax: If a dimension is called by a different name in the FDM source, you must make that substitution manually in the drill-through syntax. For example, if the Product dimension is called the Items dimension in FDM, you must substitute Items for the dimension name Product in the Essbase Studio-generated syntax. All visible dimensions in a target FDM report must be specified in the FDM URL syntax, even if, for example, you are only interested in the information in one dimension in the report. By default, the Sample FDM Template syntax picks up all intersections you specified in the Context tab of the drill-through report editor and adds them to the template syntax statement. If there are any remaining dimensions in the target FDM report, you must also include those in your syntax statement. Accessibility Top of Document Oracle Essbase Studio, though not fully accessible, does have some accessibility features built into it. These features focus on keyboard equivalents to some mouse actions. These features are always available; there is nothing to enable or disable in Essbase Studio in order for the keyboard equivalents to work. See Appendix A, Accessibility in the Essbase Studio User s Guide ( Accessibility topic in the Online Help) for information on the various keyboard equivalents available in Essbase Studio. The Oracle Essbase Studio User s Guide is available in PDF and in accessible HTML format (available as online help through the Essbase Studio Console). Additionally, the Oracle Essbase Studio New Features guide readme is available in both PDF and in accessible HTML format. Top of Document Copyright 2010, Oracle and / or its affiliates. All rights reserved. 22