Oracle® Essbase

Release 11.1.2.1.000 Patch Set (PS): 11.1.2.2.000

Readme

About this Patch. 1

Patch Type. 2

Supported Paths to this Patch. 2

Prerequisites. 2

Supported Platforms. 3

Supported Languages. 3

Defects Fixed in this Patch. 3

Known Issues in this Patch. 4

Applying this Patch. 7

Essbase Server. 8

Essbase Client 8

Common Runtime Client 9

Rolling Back this Patch. 10

Troubleshooting FAQs. 10

Documentation Updates. 11

Copying an Aggregate Storage Database. 11

Index Cache Size. 11

Configuring Teradata as a Data Source. 11

Applying AIX 5.3 Kernel Extensions Update. 13

32-bit and 64-bit Red Hat Linux Support for Teradata Data Sources. 14

Configuration for SSL Encrypted Communication with Provider Services. 14

SECFILEBACKUPINTERVAL Configuration Setting. 15

MDXQRYGOVCOUNT Configuration Setting. 15

AGENTTHREADS Configuration Setting. 15

AGTSVRCONNECTIONS Configuration Setting. 16

SERVERTHREADS Configuration Setting. 17

 

About this Patch

This Readme file describes the defects fixed in this patch set (PS) and the requirements and instructions for applying this PS.

Who should apply this patch: This PS contains defect fixes and changes that are specific to the Oracle Exalytics In-Memory machine. You should install this PS only in the following circumstances:

·         You are installing Essbase on the Exalytics In-Memory Machine, or

·         There is an urgent need for a defect fix that is included in this PS

Customers considering this PS for a platform other than the Exalytics In-Memory Machine should carefully review the list of fixed defects. If there is not a truly urgent need for a defect fix included in this PS, Oracle recommends customers install the upcoming Enterprise Performance Management (EPM) 11.1.2.2.000 release, which will contain an update, instead of this patch set. To check the availability of the EPM 11.1.2.2.000 release prior to installing this PS, visit the Oracle Software Delivery Cloud (https://edelivery.oracle.com).

Oracle highly recommends that you do extensive testing before making this patch available in a general production environment.

Caution: Once applied, you cannot roll back this patch or any other Essbase 11.1.2.2.000 component patch.

Also see the Essbase New Features.

Patch Type

This patch set replaces files in the existing installation and does not require a full installation.

This patch set includes patches for these components:

·         Essbase Server (Patch ID 11865143)

·         Essbase Client (Patch ID 11865133)

·         Common Runtime Client (Patch ID 12911847)

This patch set is cumulative and includes Essbase 11.1.2.1.102.

Supported Paths to this Patch

You can apply this patch to the following releases:

·         11.1.2.1

·         11.1.2.1.102

Prerequisites

Other Required Patches

Installation of Oracle Essbase 11.1.2.1.000 is a prerequisite for installing the server patch.

Required User Rights

The user applying the patch should be the user who was set up to install and configure EPM System products. Required user privileges or rights:

Windows:
Use the user account that has Local administrator rights and was set up for installation and configuration. This user is an administrator and is the same for all EPM System products. Assign local policies if required by the product. Such assignments typically are:
"Act as part of the operating system, Bypass traverse checking, Log on as a batch job, Log on as a service. "

UNIX/Linux:
Use the account that was used to install EPM System products and has Read, Write, and Execute permissions on $MIDDLEWARE_HOME. If you installed other Oracle products, the user who installed EPM System products must be in the same group as the user who installed the other Oracle products.
OPatches are not intended to be applied using a root user.

Supported Platforms

The Essbase Server component in this patch set is supported on Windows (32-bit and 64-bit) and Linux (64-bit) platforms only.

The Essbase Client and Common Runtime Client components in this patch set apply to all supported platforms, with the exception of Solaris 9 (also known as Solaris 2.9 or 5.9).

Supported Languages

Applies to all supported languages.

Top of Document

Defects Fixed in this Patch

Use the Defects Fixed Finder tool to review the list of defects fixed prior to release 11.1.2.2.000. This tool is available at:

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

Defect Number

Defect Fixed

• 13008515

Essbase Agent. Under some conditions, an agent deadlock occurs when invoking the ListObjects call.

• 11668895

Block Storage. Execution of calculation script, in which @ISDESC calculation function calls for nonexistent members in the database, abnormally terminates the block storage application.

• 12904542

Calculator. A large number of FIX blocks in a calc script caused the server to terminate abnormally.

• 13017954

Aggregate Storage. Aggregate storage application doesn’t start when the MDXLIMITFORMULARECURSION configuration setting is set to FALSE.

• 13073851

Essbase Agent. Under some conditions, the agent crashes because of memory corruption, which is also related to ListObjects call.

• 9893023

Calculator. Calculation times are inconsistent on fragmented databases.

• 12774338

Essbase Error. An MDX query fails in MaxL Shell and Administration Services with the following error: "Internal MDX API error: invalid cluster offsets. "

• 11843851

MDX. Basic functions used to access member properties do not return expected results on members with implicit shares and on members of dynamic hierarchies.

• 12559940

Essbase Agent. The Agent hangs when outline restructure and query execute simultaneously.

• 11738323

ESSPERL. Perl output is different on Essbase running on 64-bit Linux.

• 10222309

Spreadsheet Add-in. If Spreadsheet Add-in is installed, attempting to insert an Excel spreadsheet into a Microsoft PowerPoint document will fail, and may cause Excel to terminate abnormally.

• 13005924

Essbase Server. An email is sent or a spool file created when trigger conditions are not met.

• 10317904

Essbase Agent. Users who have been granted access as Database Manager cannot perform dimension build.

• 12890247

Aggregate Storage. CALCLOCKBLOCK configuration setting affects aggregate storage applications.

• 12665494

Spreadsheet Add-in. When an EPM client (such as Spreadsheet Add-in) is used with an Oracle client (such as Oracle ODBC) that is version 11.2.0.1, there is a path conflict wherein if the Oracle client path is specified first in the PATH system variable, the EPM client cannot be started.

• 12857741

Administration Services. When viewing active Essbase Server sessions in Administration Services Console, incorrect connect IP is shown.

• 11679774

API. Declaring variables in the incorrect order causes an error.

• 11692298

LROs. During an upgrade, LROs are not migrated.

• 12860438

API. The version number in the esb32.bas file is incorrect.

• 11663343

Administration Services. When Essbase is in Essbase native security mode, the Create/Delete Users and Groups permission in Administration Services Console does not work correctly.

• 13252949

Transparent Partition. Unable to view Dynamic Calc data retrieved through a transparent partition.

• 13011030

Dimension Build. After applying Essbase patch PSE 11.1.2.1.000_12861079, dimension build using OCI connection fails, if the data source has NULL values.

• 12579538

Transparent Partition. In a database with transparent partitions, if the TARGETTIMESERIESOPT parameter is not set in essbase.cfg, the D-T-S calculation will not execute on the source database, and the target database will display incorrect results.

Top of Document

Known Issues in this Patch

The following issues are the noteworthy known issues of this patch.

Defect Number

Issue

10159576, 12618625

Kernel. In this release, the 64-bit server has been expanded to accommodate larger cache sizes. As a result, if using an older client (9.3.x, 11.1.1.x or 11.1.2.1) with this version’s 64-bit server, the following functionality is disabled:

C-API:

·         EssGetDatabaseState — Displays zeroes for data cache, data file cache, or index cache

·         EssSetDatabaseState — Cannot set the sizes of data cache, data file cache, or index cache

·         EssGetDatabaseInfo — Displays zeroes for data cache, data file cache, or index cache

MaxL:

·         alter database DBS-NAME set data_cache_size SIZE-STRING

·         alter database DBS-NAME set data_file_cache_size SIZE-STRING

·         alter database DBS-NAME set index_cache_size SIZE-STRING

ESSCMD:

·         GETDBSTATE — Displays zeroes for data cache, data file cache, or index cache

·         SETDBSTATE — Cannot set the sizes of data cache, data file cache, or index cache

·         GETDBINFO — Displays zeroes for data cache, data file cache, or index cache

12757320, 11875089, 12757319

Filters. Filters are not created for a provisioned user when running Refresh Security Filters from within Planning to synchronize Planning with Shared Services and Essbase if the Delegated User Management option is enabled in the Shared Services console. Workaround: Disable Delegated User Management and run Refresh Security Filters from Planning again.

12757316, 11875352

Filters. Duplicate user entries can be created when running Refresh Security Filters from within Hyperion Planning to synchronize Planning with HSS and Essbase if the Delegated User Management option is enabled and the user exists in more than one external repository.

1800146, 10623580

Kernel. Direct I/O is not supported on Linux.

 

Data Mining. In Essbase and Administration Services, Data Mining is no longer enabled by default. Documentation regarding Data Mining has been removed from the Essbase and Administration Services documentation set. Data Mining may be completely removed in a future release of Essbase. For Data Mining functionality, please consider Oracle Data Mining, which is an option to the Oracle Database Enterprise Edition.

10096616

SSL. When SSL is enabled, some Essbase operations experience performance degradation.

12901508

Microsoft Visual Studio 2010. When using OPatch to install Essbase PS 11.1.2.2.000, Microsoft runtime components for Windows 32-bit and AMD 64-bit compilers are not installed. To download and install these runtime components, go to the following Microsoft websites:

Windows 32-bit platform: http://www.microsoft.com/download/en/details.aspx?id=5555

Windows AMD 64-bit platform: http://www.microsoft.com/download/en/details.aspx?id=14632

12884791

Committed Access Rollback. In committed access mode, there is a potential for a leak of free space in data files during transactional rollback.

13404757

Kernel. Logging into Essbase Server from the MaxL Shell on certain servers that run AIX 5.3 might result in the following error message:

MAXL> login essexer password;

WARNING - 1040152 - Failed to load ZT library.

WARNING - 1040156 - SSL initialization failed with error code [1040152]..

OK/INFO - 1051034 - Logging in user [essexer].

OK/INFO - 1051035 - Last login on Monday, February 07, 2011 2:57:58 PM.

OK/INFO - 1241001 - Logged in to Essbase.

This error also might occur when starting Essbase Server or running ESSCMD, and is related to initiating SSL.

Workaround: Apply the AIX 5.3 kernel extensions update on the computers on which Essbase Server and Essbase client are installed.

For information on obtaining the AIX 5.3 kernel extensions update on Oracle OTN, see "Applying AIX 5.3 Kernel Extensions Update" in the "Documentation Updates" section of this Readme.

13868678

Oracle Essbase Integration Services. After applying the 11.1.2.2.000 Common Runtime Client patch (12911847), Essbase Integration Server does not start.

Workaround:

1. Back up the following 11.1.2.1.000 folder:

·         32-bit: EssbaseRTC

·         64-bit: EssbaseRTC-64

This folder is located under EPM_ORACLE_HOME/common/.

2. To the 11.1.2.1.000 Essbase installation, apply these 11.1.2.2.000 Essbase patches:

·         Essbase Server, patch 11865143

·         Common Runtime Client, patch 12911847

See the "Applying this Patch" section.

3. Copy the backed up 11.1.2.1.000 folder (see step 1) to:

    EPM_ORACLE_HOME/products/Essbase/eis/server/bin

4. Edit the following Essbase Integration Server BAT files:

·         startup.bat

·         startOlapcmd.bat

·         startOlapbldr.bat

Edit the ARBORPATH and ESSBASEPATH to point to the following folder:

·         32-bit: EPM_ORACLE_HOME/products/Essbase/eis/server/bin/EssbaseRTC/11.1.2.0

·         64-bit: EPM_ORACLE_HOME/products/Essbase/eis/server/bin/EssbaseRTC-64/11.1.2.0

Example (64-bit):

ARBORPATH=C:/Users/qa/Oracle/Middleware/EPMSystem11R1/products/Essbase/eis/server/bin/EssbaseRTC-64/11.1.2.0

ESSBASEPATH= C:/Users/qa/Oracle/Middleware/EPMSystem11R1/products/Essbase/eis/server/bin/EssbaseRTC-64/11.1.2.0

5. Save the BAT files.

6. Start Essbase Integration Server.

13098777

Failover. In a failover cluster environment, the essbase.cfg file is shared between two Essbase nodes. As a result, the EssbaseServerHostName configuration setting in essbase.cfg works for only one node.

Workaround:

1.    Apply the 11.1.2.2.000 Essbase patches in both Essbase nodes.

See the "Applying this Patch" section.

2.    Copy the libopmness.so (UNIX/Linux) or libopmness.dll (Windows) library file from the following folder:

EPM_ORACLE_HOME/products/Essbase/EssbaseServer/bin/

to the following folder:

EPM_ORACLE_HOME/../ohs/opmn/lib

13457388

64-bit Windows Server 2008. When running 64-bit Essbase on 64-bit Windows Server 2008, some Essbase Server names are not recognized. This issue occurs when the IPv6 option is disabled on 64-bit Windows Sever 2008.

Workaround: Enable IPv6. Microsoft recommends that you leave IPv6 enabled (which is the default).

14155099, 14462547

Netezza Data Source for Essbase Studio. Unable to connect to a Netezza data source using non-streaming mode in Essbase Studio.

Workaround: In non-streaming mode, the connection to a data source is made by Essbase, not Oracle Essbase Studio. Data source drivers are specified in the Essbase configuration file (essbase.cfg). By default, some data source drivers are disabled by the presence of a semicolon (;) comment indicator at the beginning of the data source entry. In the following example, the Netezza driver is disabled.

BPM_Oracle_DriverDescriptor "DataDirect 6.1 Oracle Wire Protocol"
BPM_DB2_DriverDescriptor "DataDirect 6.1 DB2 Wire Protocol"
BPM_SQLServer_DriverDescriptor "DataDirect 6.1 SQL Server Native Wire Protocol"
;BPM_SQLServer_DriverDescriptor "SQL Server"
;BPM_Netezza_DriverDescriptor "NetezzaSQL"
BPM_Teradata_DriverDescriptor "Teradata"
;BPM_ORACLEBI_DriverDescriptor "Oracle BI Server 11g_OHXXXX"
;BPM_ORACLEBI_DriverDescriptor "Oracle BI Server"
BPM_MySQL_DriverDescriptor "DataDirect 6.1 MySQL Wire Protocol

Edit essbase.cfg to make sure that the data sources you are using are listed and are not disabled by the semicolon comment indicator.

Note: The Netezza ODBC driver must be installed on the machine on which Essbase Server runs.

Top of Document

Applying this Patch

This patch applies to all supported platforms, with the exception of Solaris 9 (also known as Solaris 2.9 or 5.9).

CAUTION: The Essbase security file (essbase.sec) in PS 11.1.2.2.000 is incompatible with Essbase 11.1.2.1 or 11.1.2.1.102, which are the supported releases for this patch. Therefore, if you apply the Essbase Server patch, it or any other Essbase 11.1.2.2.000 component patch cannot be rolled back.

NOTE: If you are using Essbase Integration Services 11.1.2.1 with Essbase 11.1.2.2.000, before applying these patches, perform the additional steps that are outlined in defect 13868678 (see the "Known Issues in this Patch" section).

This section includes important information about applying this patch to the following components.

Component

Patch ID

Essbase Server

11865143

Essbase Client

11865133

Common Runtime Client

12911847

Essbase Server

To apply this patch:

1.    Stop any Oracle services or applications that may be using Essbase files.

2.    Download and unzip the downloaded patch file, <PATCH FILE NAME>.zip, to the <EPM_ORACLE_HOME>/OPatch directory (by default, Oracle/Middleware/EPMSystem11R1/OPatch).

NOTE: <PATCH FILE NAME>.zip is the name that My Oracle Support assigns to this patch. When you download the file, a message indicates the file name.

3.    On the server on which Essbase Server runs, from a command line, change the directory to <EPM_ORACLE_HOME>/OPatch.

4.    To apply the patch, enter the following command on one line:

Windows:
opatch.bat apply <EPM_ORACLE_HOME>/OPatch/11865143 -oh <EPM_ORACLE_HOME>
-jre <MIDDLEWARE_HOME>/jdk160_21

NOTE: The default for <EPM_ORACLE_HOME> is C:/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is C:/Oracle/Middleware.

UNIX/Linux:
./opatch apply <EPM_ORACLE_HOME>/OPatch/11865143 -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>/jdk160_21 -invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

NOTE: The default for <EPM_ORACLE_HOME> is $HOME/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is $HOME/Oracle/Middleware.

5.    Restart the services that you stopped in Step 1.

Essbase Client

To apply this patch:

1.    Stop any Oracle services or applications that may be using Essbase files.

2.    Download and unzip the downloaded patch file, <PATCH FILE NAME>.zip, to the <EPM_ORACLE_HOME>/OPatch directory (by default, Oracle/Middleware/EPMSystem11R1/OPatch).

NOTE: <PATCH FILE NAME>.zip is the name that My Oracle Support assigns to this patch. When you download the file, a message indicates the file name.

3.    On the server on which the Essbase Client runs, from a command line, change the directory to <EPM_ORACLE_HOME>/OPatch.

4.    To apply the patch, enter the following command on one line:

Windows:
opatch.bat apply <EPM_ORACLE_HOME>/OPatch/11865133 -oh <EPM_ORACLE_HOME>
-jre <MIDDLEWARE_HOME>/jdk160_21

NOTE: The default for <EPM_ORACLE_HOME> is C:/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is C:/Oracle/Middleware.

UNIX/Linux:
./opatch apply <EPM_ORACLE_HOME>/OPatch/11865133 -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>/jdk160_21 -invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

NOTE: The default for <EPM_ORACLE_HOME> is $HOME/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is $HOME/Oracle/Middleware.

5.    Restart the services that you stopped in Step 1.

Common Runtime Client

To apply this patch:

1.    Stop any Oracle services or applications that may be using Essbase files.

2.    Download and unzip the downloaded patch file, <PATCH FILE NAME>.zip, to the <EPM_ORACLE_HOME>/OPatch directory (by default, Oracle/Middleware/EPMSystem11R1/OPatch).

NOTE: <PATCH FILE NAME>.zip is the name that My Oracle Support assigns to this patch. When you download the file, a message indicates the file name.

3.    On the server on which the Common Runtime Client runs, from a command line, change the directory to <EPM_ORACLE_HOME>/OPatch.

4.    To apply the patch, enter the following command on one line:

Windows:
opatch.bat apply <EPM_ORACLE_HOME>/OPatch/12911847 -oh <EPM_ORACLE_HOME>
-jre <MIDDLEWARE_HOME>/jdk160_21

NOTE: The default for <EPM_ORACLE_HOME> is C:/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is C:/Oracle/Middleware.

UNIX/Linux:
./opatch apply <EPM_ORACLE_HOME>/OPatch/12911847 -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>/jdk160_21 -invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

NOTE: The default for <EPM_ORACLE_HOME> is $HOME/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is $HOME/Oracle/Middleware.

5.    Restart the services that you stopped in Step 1.

Top of Document

Rolling Back this Patch

The Essbase security file (essbase.sec) in PS 11.1.2.2.000 is incompatible with Essbase 11.1.2.1 or 11.1.2.1.102, which are the supported releases for this patch. Therefore, if you apply the Essbase Server patch, it or any other Essbase 11.1.2.2.000 component patch cannot be rolled back.

Top of Document

Troubleshooting FAQs

How can I find out which releases and patches of EPM System products are installed in a deployment?

In EPM System Release 11.x, you can use the lsinventory command to OPatch to find the release and patches that are installed in an Oracle Home. For example, enter the following command on one line:

Windows:

opatch.bat lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_21

NOTE: The default for <EPM_ORACLE_HOME> is C:/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is C:/Oracle/Middleware.

UNIX/Linux:

./opatch lsinventory -oh <EPM_ORACLE_HOME> -jdk <MIDDLEWARE_HOME>/jdk160_21

NOTE: The default for <EPM_ORACLE_HOME> is $HOME/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is $HOME/Oracle/Middleware.

Why do I get the following patch conflict error message when running OPatch?

If the patch that you apply conflicts with a previously applied patch, you may receive the following error message when running OPatch:

Patch(es) <PreviousPatch#> conflict with the patch currently being installed (<NewPatch#>).

If you continue, patch(es) <PreviousPatch#> will be rolled back and the new patch (<NewPatch#>) will be installed.

If a merge of the new patch (<NewPatch#>) and the conflicting patch(es) (<PreviousPatch#>) is required, contact Oracle Support Services and request a Merged patch.

This error is returned when one patch attempts to update a previously patched file. When this conflict happens, you can either (1) roll back the previous patch and apply the new patch (this action might be appropriate if the previous patch was not critical) or (2) request a "merged patch" consisting of the new patch and the patch that it conflicts with. To request a merged patch, contact your Oracle Support representative.  

Why do I get the OUI-67078 warning message when applying OPatch?

This warning means that the patch being applied is a superset of a patch already on the deployment and the existing patch will be rolled back. The following snippet shows the context of this warning.

The following warnings have occurred during OPatch execution:
1) OUI-67078:Interim patch 12345678 is a superset of the patch(es) [77777777] in OH C:\Hyperion
-----------------------------------------------------------------------------------
OPatch Session completed with warnings.

Top of Document

Documentation Updates

Copying an Aggregate Storage Database

To copy all of the data in an aggregate storage application, you must merge all incremental data slices into the main database slice. Data in unmerged incremental data slices is not copied.

Index Cache Size

The following information updates the index cache size information in the Essbase 11.1.2.2.000 documentation.

Minimum value: 1 MB (1,048,576 bytes)

Maximum values:

32-bit Essbase: 4 GB

64-bit Essbase: 256 TB

Default values:

Buffered I/O: 1 MB

Direct I/O: 10 MB

The minimum and maximum values apply to buffered and direct I/O.

Configuring Teradata as a Data Source

This topic replaces the topic named “Establishing a Connection to a Teradata Database when Using Essbase with OPMN” that appeared in a previous version of this Readme.

To configure Teradata as a data source:

1.    Install Teradata drivers, which you must obtain from Teradata.

·         Essbase Studio uses JDBC drivers. The JDBC Teradata driver must be installed on the computer on which Essbase Studio Server runs.

Essbase Studio uses the JDBC Teradata driver to deploy cubes in streaming mode.

To deploy cubes in non-streaming mode, the ODBC Teradata driver must be installed on the computer on which Essbase Server runs.

·         Essbase uses ODBC drivers. The ODBC Teradata driver must be installed on the computer on which Essbase Server runs.

2.    Stop Essbase from the Windows Services panel using the Oracle Process Manager and Notification (OPMN) service: EPM_epmsystem1.

3.    Backup the OPMN configuration file (opmn.xml).

For example:

C:\Oracle\Middleware\user_projects\epmsystem1\config\OPMN\opmn\opmn.xml

4.    Open the opmn.xml file in a text editor.

5.    To properly load the Teradata drivers, the opmn.xml file must include a statement that points to the location of the Teradata libraries.

a.    Locate the following statement in the opmn.xml file:

<variable id="ESS_CSS_JVM_OPTION7" value="-Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration"/>

b. After this statement, add a statement similar to the following one:

<variable append="true" id="PATH" value="C:\Program Files\Teradata\Client\14.00\Shared ICU Libraries for Teradata\lib"/>

6.    When using Teradata data sources with Essbase, and using OPMN to monitor and control the Essbase Agent process, you must update the opmn.xml file with variables for the operating system you are using.

Note: The absolute path value cannot contain spaces. The examples of absolute path values are based on a 64-bit machine configuration.

64-bit Windows

Add these variables:

·         TWB_ROOT: Teradata root

·         PATH: Teradata shared libraries

·         PATH: Teradata client DLL libraries

·         PATH: Teradata Call-Level Interface Version 2 routines

·         PATH: Teradata message DLL libraries

64-bit Windows example:

<variable id="TWB_ROOT" value="C:\PROGRA~1\Teradata\Client\14.00"/>

<variable append="true" id="PATH" value="C:\PROGRA~1\Teradata\Client\14.00\SHARED~1\lib"/>

<variable append="true" id="PATH" value="C:\PROGRA~1\Teradata\Client\14.00\TERADA~1\bin64"/>

<variable append="true" id="PATH" value="C:\PROGRA~1\Teradata\Client\14.00\CLIv2"/>

<variable append="true" id="PATH" value="C:\PROGRA~1\Teradata\Client\14.00\TERADA~1\msg64"/>

64-bit AIX

Add these variables:

·         LIBPATH: Teradata ODBC libraries

·         LIBPATH: Teradata shared libraries

·         LIBPATH: ODBC components needed to load Teradata ODBC drivers

·         LIBPATH: Teradata client libraries

·         COPERR: Directory where the errmsg.txt file resides

·         NLSPATH: Teradata message libraries

64-bit AIX example:

<variable append="true" id="LIBPATH" value="/opt/teradata/client/ODBC_64/lib"/>

<variable append="true" id="LIBPATH" value="/opt/teradata/client/13.10/tdicu/lib64"/>

<variable append="true" id="LIBPATH" value="/usr/odbc/lib:/usr/odbc/drivers"/>

<variable append="true" id="LIBPATH" value="/usr/lib:/usr/teragss/aix-power/client/lib"/>

<variable id=" COPERR" value="/usr/libperion/essbase"/>

<variable id="NLSPATH" value="/opt/teradata/client/13.10/odbc_32/msg/%N"/>

<variable append="true" id="NLSPATH" value="/usr/lib/nls/msg/%L/%N"/>

<variable append="true" id="NLSPATH" value="/usr/lib/nls/msg/%L/%N.cat"/>

64-bit LINUX

Add these variables:

·         TWB_ROOT: Teradata root

·         TD_ICU_DATA: Teradata shared libraries

·         NLSPATH: Teradata ODBC message libraries

·         COPERR: Directory where the errmsg.txt file resides

·         COPLIB: Directory where the libcliv2.so library file resides

·         LD_LIBRARY_PATH: Teradata libraries

·         PATH: Teradata client directories

Note: The errmsg.txt and libcliv2.so files typically reside in the same directory. Therefore, the value for the COPERR and COPLIB variables is typically identical.

64-bit LINUX example:

<variable id="TWB_ROOT" value="/opt/teradata/client/13.10/tbuild"/>

<variable id="TD_ICU_DATA" value="</opt/teradata/client/13.10/tdicu/lib64> "/>

<variable id="NLSPATH" value="</opt/teradata/client/13.10/odbc_64/msg/%N > "/>  

<variable append=”true” id=”NLSPATH” value=”/opt/teradata/client/13.10/tbuild/msg64/%N”/>

<variable id="COPERR" value="/usr/lib64"/>

<variable id="COPLIB" value="/usr/lib64"/>

<variable append=”true” id=”LD_LIBRARY_PATH” value=”/opt/teradata/client/13.10/tbuild/lib64”/>

<variable append=”true” id=”LD_LIBRARY_PATH” value=”/usr/lib64”/>

<variable append=”true” id=”PATH” value=”/opt/teradata/client/13.10/tbuild/bin”/>

<variable append=”true” id=”PATH” value=”/opt/teradata/client/13.10/tbuild/lib64”/>

7.    Save the opmn.xml file.

8.    Start Essbase from the Windows Services panel using the Oracle Process Manager and Notification (OPMN) service (EPM_epmsystem1).

9.     Verify the following:

·         Essbase: Use the Data Prep Editor in Essbase Administration Services Console to connect to a Teradata database using a DNS.

·         Essbase Studio: Perform a cube deployment in non-streaming mode, which uses the Teradata ODBC driver.

Applying AIX 5.3 Kernel Extensions Update

See the description of defect 13404757 in the "Known Issues" section of this Readme.

If you have installed Oracle Database 11g Release 2 (11.2.0.1.0), the AIX 5.3 kernel extensions update file (rootpre.sh) is included. Or you can obtain the file from the Oracle Software Delivery Cloud site.

1.    Log into Oracle Software Delivery Cloud at:

https://edelivery.oracle.com

2.    On the “Media Pack Search” page, enter the following information:

·         For Select a Product Pack, select Oracle Database.

·         For Platform, select IBM AIX on POWER Systems (64-bit).

3.    Click Go.

4.    In the results list, select Oracle® Database 11g Release 2 (11.2.0.1.0) Media Pack for IBM AIX on POWER Systems (64-bit), and then click Continue.

5.    On the “Oracle® Database 11g Release 2 (11.2.0.1.0) Media Pack for IBM AIX on POWER Systems (64-bit)” page, click Download next to Oracle Database 11g Release 2 (11.2.0.1.0) for IBM AIX on POWER Systems (64-bit) (Part 1 of 2).

6.    Unarchive the download file.

7.    Run the rootpre.sh file on the computers on which Essbase Server and Essbase client are installed.

32-bit and 64-bit Red Hat Linux Support for Teradata Data Sources

The following information updates the Red Hat Linux information in the "Using Teradata Data Sources" topic in the Oracle Essbase SQL Interface Guide:

Essbase supports Teradata Parallel Transporter (TPT) 12 with the Teradata 12 ODBC driver on 32-bit and 64-bit Red Hat Linux platforms.

Configuration for SSL Encrypted Communication with Provider Services

To configure Essbase for encrypted (SSL) communication with Provider Services, you must perform a configuration task to enable the Essbase libcurl library to set up a secure channel to Provider Services.  This is required to enable secure connections to be made between Essbase and Provider Services using logical Essbase cluster names.

Use the following three configuration options to either disable peer verification, or provide the location of the certificate authority (CA) certificates. To complete this configuration, set the following environment variables, using the operating system command line:

API_DISABLE_PEER_VERIFICATION=1

Set this variable if the connection goes through SSL, but does not need a certificate. Essbase  provides data encryption, but not authentication.

If API_DISABLE_PEER_VERFICATION is not set, or is set to 0, you must set up a certificate. To establish a secure connection with Provider Services, Essbase requires a CA signing of a Provider Services certificate, to provide authentication for the Provider Services server. You can specify either a file or a directory which includes the certificate. Choose one of the following options:

API_CAINFO=CA certificate file path

or

API_CAPATH=directory path containing CA certificates

The environment variables described are only applied when logging with a Provider Services URL that starts with https. Logins with the http URL are directed through TCP/IP.

SECFILEBACKUPINTERVAL Configuration Setting

The SECFILEBACKUPINTERVAL configuration setting topic in the Oracle Essbase Technical Reference incorrectly states the description of the n argument. The following information is correct:

SECFILEBACKUPINTERVAL n

n—Specifies the amount of time in seconds.

The default value is 300 seconds (which is five minutes). A value of 0 means that the essbase.sec file will not be backed up. Other than 0, the value cannot be less than 300.

MDXQRYGOVCOUNT Configuration Setting

(13932483) A new Essbase.cfg setting, MDXQRYGOVCOUNT, is added as a query governor (along with the existing configuration settings, QRYGOVEXECTIME and QRYGOVEXECBLK) to help you limitations set on MDX queries.

MDXQRYGOVCOUNT

Initializes a counter (number of check conditions) to control how often Essbase checks for conditions that would warrant termination of an MDX query. Using this counter can reduce or increase the default number of checks (1000); reducing the number of checks (by setting n higher) improves performance. The counter starts at n and decrements until the counter reaches zero: at that time Essbase performs a check.

Syntax

MDXQRYGOVCOUNT [appname [dbname]] n

·         appname —Optional. Applies the checking counter to the application specified. If you specify appname, you must also specify a value for n, or Essbase Server ignores this setting. If you do not specify an application, then you cannot specify a database, and the counter applies to all applications and databases on Essbase Server. If you specify a value for appname and do not specify a value for dbname, the counter applies to all databases in the specified application.

·         dbname —Optional. Must be used with appname and n, or Essbase Server ignores this setting. If you specify dbname, appname, and n, the counter is applied only to the specified database.

·         n —Integer specifying the counter (number of check conditions) that Essbase Server checks for conditions that warrant query termination. You must specify this parameter or Essbase Server ignores this setting. If do not specify appname or dbname, the counter applies to the entire server. The default value is 1000. The minimum value is 100, and the maximum value is 5000.

Notes

You can use the Esc key to cancel any query running from MaxL Shell.

Example

MDXQRYGOVCOUNT 1500

AGENTTHREADS Configuration Setting

The following description of the AGENTTHREADS configuration setting is more accurate than the topic in the Oracle Essbase Technical Reference.

AGENTTHREADS

Specifies the maximum number of threads that the Agent process (ESSBASE) can spawn. Agent threads are used for logging in and out of Essbase Server, starting and stopping an application, etc.

One agent thread is used in conjunction with a thread spawned by the AGTSVRCONNECTIONS configuration setting to allow the initial login through the Agent and to establish the first connection to an application and database. When a connection is requested, the Agent assigns a thread to the request and releases the thread when the connection is made.

The rest of the agent threads are used for other Agent tasks unrelated to AGTSVRCONNECTIONS. Once connected, AGTSVRCONNECTIONS threads are no longer used. Client requests are managed by threads spawned by the application process (ESSSVR).

Syntax

AGENTTHREADS n

n: Specifies the number of threads that the Agent process (ESSBASE) can spawn.

·         32-bit platform: 2 to 500, inclusive

·         64-bit platform: 2 and 1024, inclusive

The default value is 5.

Notes

·         Oracle strongly recommends that you use the default value when running Essbase on a 32-bit platform.

·         While the actual maximum value you can set is 500 (32-bit platform) or 1024 (64-bit platform), the maximum number of threads an operating system can handle might be much lower. Before specifying a value greater than the default value, check with your system administrator, as higher values can significantly consume system resources.

·         If you specify a number less than 2, over the maximum, or a decimal value, Essbase overrides the value with a closely approximate value of its own.

·         One thread is required for each initial connection to an application and database.

Example

AGENTTHREADS 15

AGTSVRCONNECTIONS Configuration Setting

The following description of the AGTSVRCONNECTIONS configuration setting is more accurate than the topic in the Oracle Essbase Technical Reference.

AGTSVRCONNECTIONS

Specifies the maximum number of threads that Essbase can spawn to allow the first connection to an application and database, negotiated between the Agent process (ESSBASE) and application process (ESSSVR). AGTSVRCONNECTIONS threads make the Agent process (ESSBASE) communicate with the application process (ESSSVR).

Each AGTSVRCONNECTIONS thread uses one Agent process (ESSBASE) thread only while logging in and connecting to an application and database. Once connected, client requests are managed by threads spawned by the application process (ESSSVR).

Syntax

AGTSVRCONNECTIONS n

n: Specifies the maximum number of AGTSVRCONNECTIONS threads that Essbase can spawn.

·         Default value: 5

·         Minimum value: 1

Caution! Oracle recommends a maximum value of 10.

Notes

·         Make sure you have enough open file descriptors configured in the operating system to accommodate the value you set for AGTSVRCONNECTIONS.

·         Consider specifying a value greater than the default value, if you are expecting a large number of users to login and select the same application within a short period of time.

Example

AGTSVRCONNECTIONS 7

Sets the maximum number of AGTSVRCONNECTIONS threads that Essbase can spawn to 7.

SERVERTHREADS Configuration Setting

The following description of the SERVERTHREADS configuration setting is more accurate than the topic in the Oracle Essbase Technical Reference.

SERVERTHREADS

Overrides the default value of the number of threads that the application process (ESSSVR) can spawn. Application threads are used in calculations, client requires, administrative activities, etc.

When a transaction is requested, the application process (ESSSVR) assigns a thread to the transaction and releases the thread when the transaction is completed.

Syntax

SERVERTHREADS [appname] n

·         appname—Optional. Specifies an application; the SERVERTHREADS setting applies to all databases within the named application.

If you do not specify an application, the setting applies to all applications and databases on Essbase Server.

·         n—Specifies the number of threads that the application process (ESSSVR) can spawn.

·         32-bit platform: 20 to 500, inclusive

·         64-bit platform: 20 to 1024, inclusive

The default value is 20.

If you specify a value that is:

·         Less than the minimum, Essbase interprets the value as 20

·         Greater than the maximum, Oracle Essbase interprets the value as 500 (32-bit platform) or 1024 (64-bit platform)

Notes

·         While the actual maximum value you can set is 500 (32-bit platform) or 1024 (64-bit platform), the maximum number of threads an operating system can handle might be much lower. Before specifying a value greater than the default value, check with your system administrator, as higher values can significantly consume system resources.

·         If the computer on which Essbase Server runs freezes while running multiple reports simultaneously, increase the value of SERVERTHREADS by one for each report you run.

·         Each application thread may create child threads for tasks such as parallel calculation, parallel data load or export, and parallel restructuring. If the total number of running threads is too high, threads may lose efficiency in contending for server resources. To manage thread contention, use the MAXTOTALACTIVETRANSACTIONS and MAXACTIVEUPDATETRANSACTIONS settings.


Example

SERVERTHREADS 25

Allows all applications on Essbase Server to spawn up to 25 threads.

SERVERTHREADS Sample 100

Allows the Sample application on Essbase Server to spawn up to 100 threads.

Top of Document

 

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