Oracle® Essbase

Readme

Release 12.2.1.2.0


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

Authors: EPM Information Development Team

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS:

Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

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

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. Microsoft, Windows, PowerPoint, Word, Excel, Access, Office, Outlook, Visual Studio, Visual Basic, Internet Explorer, Active Directory, and SQL Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.


Table of Contents:

Purpose

Administration Services and Essbase Studio 11.1.2.4.008 or Later Are Supported in Essbase 12.2.1.2.0

Unsupported Features in Essbase 12.2.1.2.0

Installation Information

Supported Platforms

Supported Paths to this Release

Defects Fixed in this Release

Known Issues in this Release

Documentation Updates

Documentation Feedback

Accessibility Considerations

Purpose

This document includes important, late-breaking information about this release of Oracle Essbase. Review this Readme thoroughly before installing Essbase in an Oracle Business Intelligence 12.2.1.2.0 environment.

Administration Services and Essbase Studio 11.1.2.4.008 or Later Are Supported in Essbase 12.2.1.2.0

Supported components for Essbase 12.2.1.2.0:

  • Essbase 12.2.1.2.0

  • Oracle Hyperion Provider Services 12.2.1.1.0

  • Oracle Essbase Administration Services 11.1.2.4.008 or later

  • Oracle Essbase Studio 11.1.2.4.008 or later

Note:

Administration Services and Essbase Studio releases earlier than 11.1.2.4.008 are not supported with Essbase 12.2.1.2.0.

Unsupported Features in Essbase 12.2.1.2.0

These features are not supported in this release:

  • Cube Deployment Service (CDS)

  • Essbase BI Acceleration

Any references to CDS, Essbase BI Acceleration, and Essbase BI Acceleration Wizard in the Essbase documentation should be ignored.

Installation Information

See the Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence for information on installing Essbase in the Oracle Business Intelligence 12.2.1.2.0 environment.

Supported Platforms

See the Oracle Fusion Middleware 12c Certifications on the Oracle Fusion Middleware Supported System Configurations page on the Oracle Technical Network at http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html.

Supported Paths to this Release

You can upgrade to Essbase 12.2.1.2.0 from the Essbase 12.2.1.0.0 or 12.2.1.1.0 releases only.

Note:

In Essbase 12.2.1.2.0, you cannot migrate databases that were created in 11.1.2.4.xxx versions of Essbase. However, you can copy dimension build rules files and data load rules files from an Essbase 11.1.2.4.xxx database to create a new database in release 12.2.1.2.0. Then you can define other artifacts (such as location aliases, partitions, and substitution variables) in the 12.2.1.2.0 database. You can also copy calculation scripts created in Essbase 11.1.2.4.xxx for use in databases created in 12.2.1.2.0.

Defects Fixed in this Release

This section includes defects fixed in Release 12.2.1.2.0. To review the list of defects fixed between earlier releases, use the Defects Fixed Finder. This tool enables you to identify the products you own and your current implementation release. With a single click, the tool quickly produces a customized report of fixed-defect descriptions with their associated platforms and patch numbers. This tool is available at:

https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1292603.1

There are no noteworthy fixed defects in this release.

Known Issues in this Release

The following is the noteworthy known issue for this release.

  • 21875962, 21888775 -- Essbase Java Agent fails to start out of the box when Essbase is deployed in BI 12.2.1.0.0 or BI 12.2.1.1.0, which is configured with DB2.

    Workaround:

    1. Login to the Oracle WebLogic Server Administration console.

    2. Navigate to Services, then Data Sources, then wlsservices_datasource, and then the Connection Pool tab.

    3. Use the Lock & Edit option.

    4. In the Properties section, change the user property from:

      user=<RCU_PREFIX>_WLS_RUNTIME

      To:

      user=<RCU_PREFIX>_WLS

      For example:

      user=MYBI_WLS
      oracle.net.CONNECT_TIMEOUT=10000
      SendStreamAsBlob=true
    5. Save the changes.

    6. Navigate to Environment, then Clusters, then bi_cluster, and then the Migration tab.

    7. In the Auto Migration Table Name field, prepend <RCU_PREFIX>_WLS_RUNTIME to the exiting ACTIVE value:

      <RCU_PREFIX>_WLS_RUNTIME.ACTIVE

      Using the example from Step 4:

      MYBI_WLS_RUNTIME.ACTIVE
    8. Save the changes.

    9. Use the Activate Changes option to makes these changes take effect.

    10. Restart the BI 12.2.1.1.0 environment.

  • 23259118 -- Creating an application might fail if IPV4 is disabled and only IPV6 is enabled in the environment in which Essbase is installed.

    Workaround:

    If IPV4 is disabled, enable IPV4 and restart the BI 12.2.1.1.0 environment.

  • 22596350 -- Drill-through reports with recursive hierarchy based cube deployments from Essbase Studio do not work if Dynamic Time Series functions exist in the Oracle Smart View for Office grid.

Loading ODBC Drivers in Release 12.2.1.2.0

In releases previous to 12.2.1.2.0, Essbase loads ODBC drivers by reading the odbcinst.ini from $DOMAIN_HOME/config/fmwconfig/bienv/core/odbcinst.ini.

Starting in release 12.2.1.2.0, Essbase discovers ODBC drivers by reading the common Data Direct configuration file that is used by the BI stack. The common Oracle Data Direct configuration file is $DOMAIN_HOME/config/fmwconfig/biconfig/core/ddpath.properties.

By default, in release 12.2.1.2.0, this configuration file points to $BI_ORACLE_HOME/modules/oracle.bi.datadirect.odbc/8.0.1; the odbcinst.ini used by Essbase is under this location.

Note:

the BPM driver descriptor based entries in the Essbase configuration file (essbase.cfg) correspond to the driver names listed in the odbcinst.ini. If you change the driver version and location defined in ddpath.properties, then you need to modify the driver descriptor entries in essbase.cfg so that they match the drivers loaded in the corresponding odbcinst.ini.

Example

If you modify ddpath.properties to point to Data Direct version 7.1.4, edit the value as follows:

DD_PATH=/ExampleRoot/Oracle/bi/modules/oracle.bi.datadirect.odbc/7.1.4

This makes Essbase point to /ExampleRoot/Oracle/bi/modules/oracle.bi.datadirect.odbc/7.1.4/odbcinst.ini and load the version 7.1.4 drivers. You must align the driver descriptor entries in essbase.cfg to match the ones loaded through this odbcinst.ini. For example:

BPM_DB2_DriverDescriptor        "Oracle 7.1 DB2 Wire Protocol"
BPM_MySQL_DriverDescriptor      "Oracle 7.1 MySQL Wire Protocol"
BPM_Oracle_DriverDescriptor     "Oracle 7.1 Oracle Wire Protocol"
BPM_SQLServer_DriverDescriptor  "Oracle 7.1 SQL Server Wire Protocol"
BPM_Teradata_DriverDescriptor   "Oracle 7.1 Teradata"

Oracle Help Center Libraries to Use for the Essbase 12.2.1.2.0 Release

For the Essbase 12.2.1.2.0 release, use these Oracle help center libraries:

  • Oracle Essbase Documentation Release 12.2.1.0.0 library—The guides available on this library pertain to the Essbase 12.2.1.2.0 release. Updated documents:

    • The Oracle Essbase Database Administrator's Guide was updated for Release 12.2.1.1.0

    • In addition to the Essbase Readme for 12.2.1.0.0, this Essbase 12.2.1.2.0 Readme is also on the library.

  • Oracle Essbase Documentation Release 11.1.2.4.000 library—If you are using Oracle Essbase Administration Services 11.1.2.4.008 or Oracle Essbase Studio 11.1.2.4.008 with Essbase 12.2.1.2.0, use the respective product documentation on this library.

Adding 7.1 Driver Descriptors to the odbcinst.ini File (23317170)

The process for adding 7.1 driver descriptor information involves opening the odbcinst.ini file in one location to copy the driver descriptor information and then opening the odbcinst.ini file in another location to paste the driver descriptor information.

To add 7.1 driver descriptors to the odbcinst.ini file:

  1. Navigate to the following directory:

    Oracle_Home/bi/modules/oracle.bi.datadirect.odbc/8.0.1
  2. Open the odbcinst.ini file.

    The odbcinst.ini file in this directory contains a list of supported drivers and driver descriptor information.

  3. Copy the descriptor information for the driver that you want to use.

    For example, for the 7.1 DB2 driver, copy this block of text:

    [Oracle 7.1 DB2 Wire Protocol]
    Driver=/Oracle_Home/bi/modules/oracle.bi.datadirect.odbc/7.1.5/lib/ARdb227.so
    APILevel=0
    ConnectFunctions=YYY
    DriverODBCVer=3.52
    FileUsage=0
    HelpRootDirectory=/Oracle_Home/bi/modules/oracle.bi.datadirect.odbc/7.1.5/help
    Setup=Oracle_Home/bi/modules/oracle.bi.datadirect.odbc/7.1.5/lib/ARdb227.so
    SQLLevel=0

    Note:

    In the odbcinst.ini file, absolute paths are given for the Driver, HelpRootDirectory, and Setup paths. The Oracle_Home variable is used in the documentation for illustration purposes only. In the odbcinst.ini file, you cannot use variables in the path.

  4. Navigate to the following directory:

    domain_home/bi/config/fmwconfig/bienv/core
  5. Open the odbcinst.ini file in this directory and make these changes:

    1. Somewhere after the [ODBC Drivers] section, add a new line and paste the driver description information that you copied in step 3.

      For example, for the 7.1 DB2 driver, paste this block of text:

      [Oracle 7.1 DB2 Wire Protocol]
      Driver=/Oracle_Home/bi/modules/oracle.bi.datadirect.odbc/7.1.5/lib/ARdb227.so
      APILevel=0
      ConnectFunctions=YYY
      DriverODBCVer=3.52
      FileUsage=0
      HelpRootDirectory=/Oracle_Home/bi/modules/oracle.bi.datadirect.odbc/7.1.5/help
      Setup=Oracle_Home/bi/modules/oracle.bi.datadirect.odbc/7.1.5/lib/ARdb227.so
      SQLLevel=0
    2. In the [ODBC Drivers] section at the beginning of the odbcinst.ini file, add a new line and enter the name of the driver, excluding the brackets ([ ]), using this syntax:

      driver_name=Installed

      For example, for the 7.1 DB2 driver, enter this line of text:

      Oracle 7.1 DB2 Wire Protocol=Installed
    3. Save the odbcinst.ini file in the $domain_home/bi/config/fmwconfig/bienv/core directory.

      The saved odbcinst.ini file might look similar to this example:

      [ODBC Drivers]
      Oracle 7.1 Oracle Wire Protocol=Installed
      Oracle 7.1 DB2 Wire Protocol=Installed
      Oracle 7.1 SQL Server Wire Protocol=Installed
      Oracle BI Server=Installed
      
      [Oracle 7.1 Oracle Wire Protocol]
      Driver=/Oracle_Home/bi/modules/oracle.bi.datadirect.odbc/7.1.5/lib/ARora27.so
      APILevel=0 
      ConnectFunctions=YYY 
      DriverODBCVer=3.52 
      FileUsage=0 
      HelpRootDirectory=/Oracle_Home/bi/modules/oracle.bi.datadirect.odbc/7.1.5/help
      Setup=/Oracle_Home/bi/modules/oracle.bi.datadirect.odbc/7.1.5/lib/ARora27.so
      SQLLevel=0 
      
      [Oracle 7.1 DB2 Wire Protocol]
      Driver=/Oracle_Home/bi/modules/oracle.bi.datadirect.odbc/7.1.5/lib/ARdb227.so
      APILevel=0
      ConnectFunctions=YYY
      DriverODBCVer=3.52
      FileUsage=0
      HelpRootDirectory=/Oracle_Home/bi/modules/oracle.bi.datadirect.odbc/7.1.5/help
      Setup=/Oracle_Home/bi/modules/oracle.bi.datadirect.odbc/7.1.5/lib/ARdb227.so
      SQLLevel=0
      
      [Oracle 7.1 SQL Server Wire Protocol]
      Driver=/Oracle_Home/bi/modules/oracle.bi.datadirect.odbc/7.1.5/lib/ARsqls27.so
      APILevel=1
      ConnectFunctions=YYY
      DriverODBCVer=3.52
      FileUsage=0
      HelpRootDirectory=/Oracle_Home/bi/modules/oracle.bi.datadirect.odbc/7.1.5/help
      SQLLevel=0
      
      [Oracle BI Server] 
      Driver=/Oracle_Home/bi/bifoundation/server/bin/libnqsodbc64.so 
      APILevel=3 
      ConnectFunctions=YYN 
      DriverODBCVer=3.52 
      FileUsage=0 
      SQLLevel=2

The following information updates the “SSL for Essbase” documentation in the Oracle Essbase Database Administrator's Guide for 12.2.1.0.0.

Location of the orapki Command-Line Tool

In Essbase 12.2.1.1.0, the Oracle public key infrastructure (PKI) command-line tool, orapki, is located in the following directory:

ORACLE_HOME/oracle_common/bin

(23097401)

Configuring a BI Client to Connect to Essbase in SSL Mode

When Essbase is in SSL mode, you must set up the certificates needed for a BI client to connect to Essbase as a datasource while creating a new BI repository.

The following instructions assume that you have completed the instructions in the “Setting Up Wallets” section of the Oracle Essbase Database Administrator's Guide for setting up the root, Essbase Server, and Essbase client wallets and for configuring the WALLETPATH configuration setting in the essbase.cfg file.

To configure a BI client to connect to Essbase in SSL mode:

  1. From the Essbase Server installation, copy the cwallet.sso and ewallet.p12 files to the BI client installation in the following directory:

    ORACLE_HOME\oui\config\fmwconfig\biconfig\essbase\walletssl

    Note:

    This directory is where configuration files are typically located in a BI client installation. However, you can copy these files to another directory that is within the BI client installation.

  2. Create an essbase.cfg file that includes only the WALLETPATH configuration setting that specifies the directory in step 1.

  3. Copy this version of the essbase.cfg file to the following directory:

    ORACLE_HOME\oui\config\fmwconfig\biconfig\essbase
  4. Set the ESSBASE_CONFIG_PATH variable to add the path to the directory where the essbase.cfg is located in step 3 to the BI client nqinit.cmd file so that the BI client picks up the Essbase wallet files when loading. For example:

    ESSBASE_CONFIG_PATH=ORACLE_HOME\oui\config\fmwconfig\biconfig\essbase to ORACLE_HOME\bi\bifoundation\server\bin\nqinit.cmd

The BI client should be able to connect to Oracle Essbase in secure mode using this URL syntax:

Host:secure_port:secure

(23097447)

ESSSVRSTARTUPWAITTIME Configuration Setting

Specifies the maximum amount of time (in seconds) that the Essbase Java Agent waits for the application process (ESSSVR) to start. If the process does not start before the specified maximum amount of time, the start up is considered failed.

Syntax:

ESSSVRSTARTUPWAITTIME n

n—Specifies the maximum number of seconds that the Essbase Java Agent waits for the application process (ESSSVR) to start. The default value is 180 seconds.

Example:

ESSSVRSTARTUPWAITTIME 300

Specifies 300 seconds as the maximum number of seconds that the Essbase Java Agent waits for the application process (ESSSVR) to start.

(23198805)

FUSIONAPPID Configuration Setting Value is Lowercase (obi)

In the 12.2.1.0.0 version of the Oracle Essbase Technical Reference, the syntax for the FUSIONAPPID configuration setting is expressed as:

FUSIONAPPID OBI

The value of this configuration setting should be lowercase. Revised FUSIONAPPID configuration setting syntax:

FUSIONAPPID obi

(21975522)

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.

Documentation Feedback

Send feedback on product documentation to the following email address: EPMdoc_ww@oracle.com.

Follow EPM Information Development on these social media sites:

Accessibility Considerations

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