Oracle® Essbase

Readme

Release 11.1.2.2.200


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

Updated: December 2014

Authors: EPM Information Development Team

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.

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, 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.

This software or hardware and documentation may provide access to or information on 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. 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.


Table of Contents:

Purpose

Documentation

Defects Fixed in this Release

Known Issues

Documentation Updates

Accessibility Considerations

Purpose

This document includes important, late-breaking information about this release of Oracle Essbase. Review this Readme thoroughly before installing Essbase.

Documentation

For installation information, platform support and other Oracle Business Intelligence Enterprise Edition documentation, please see: http://www.oracle.com/technetwork/middleware/bi-enterprise-edition/documentation/index.html.

Defects Fixed in this Release

14092254 - On aggregate storage databases, when using the MaxL deploy statement to create hierarchies (outside of Accounts) with user-defined members at the top level and dimension elements for the subsequent levels, the MaxL Shell returns an error.

Known Issues

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

  • The Solaris 10 Operating System requires, at a minimum, the Update 10 Patch Set. Without this patch set level, starting Essbase results in the following error message in the console~AGENT~1.log file:

    ld.so.1: ESSBASE: fatal: relocation error: file /oracle/obiee/mwhome/Oracle_BI1/products/Essbase/EssbaseServer/bin/libesssdu.so: symbol smt_pause: referenced symbol not found

    The console~AGENT~1.log file is located in the following directory: diagnostics/logs/Essbase/essbaseserver1.

  • 14776250 Linux 6 For a BI Shiphome installation of Essbase, on Oracle Enterprise Linux 6 (OEL6), you must set ulimit -u and ulimit -n to 4096 or higher.

  • 13974353, 13944879 High Availability.Essbase fails to start when Essbase is configured in high-availability mode as an active/passive failover cluster and the BI database is configured on Oracle Real Application Clusters (RAC) using the non-SCAN method, in which the hostname for each RAC node is specified.

    Workaround:

    • If the Oracle database version is 11gR2 or later, configure RAC using the SCAN based method and reconfigure the database of your Oracle Business Intelligence system using the corresponding SCAN virtual host name.

    • If the Oracle database version is earlier than 11gR2 and Essbase does not start because the RAC primary node fails:

    1. Run the following script to change the “dbHost” property from primary host to secondary host:

      Syntax:

      <epmsys_registry SCRIPT> updateproperty <COMPONENT_ID_OF_DATABASE_CONN>/@dbHost <SecondaryHostName> 
      Example: ./epmsys_registry.sh updateproperty \#45137119ef5394fe6e9ec3e113662699e3aS7fe0/@dbHost mySecondaryRacNode.oracle.com 
      
    2. If the Oracle Database port of the secondary RAC node is different from the primary node, run the same script to change the “dbPort” property:

      Syntax:

      <epmsys_registry SCRIPT> updateproperty <COMPONENT_ID_OF_DATABASE_CONN>/@dbPort <SecondaryNodePort> 
      Example: ./epmsys_registry.sh updateproperty \#45137119ef5394fe6e9ec3e113662699e3aS7fe0/@dbPort 1522 
      
    3. Start Essbase.

    Note:

    The instructions for a RAC database earlier than 11gR2 are temporary, because Essbase continues to work as long as the secondary RAC node is alive. If the secondary RAC node goes down and Essbase is expected to work, follow the same instructions to reconfigure the database in the registry to point to the most preferred and alive node in the RAC database.

  • 14210382, 14210563 Essbase Agent. When displaying a list of database-related file artifacts, for example, when using MaxL display object or API function EssListObject, the sort order of the list is not consistent across operating systems.

  • 14120458, 14128981 Oracle Call Interface (OCI) Connecting to an Oracle data source with Oracle Call Interface (OCI) is not available in this version, whether using Oracle Essbase Studio, the MaxL deploy statement, or Data Prep Editor in Oracle Essbase Administration Services.

  • 13637169 -- AIX (64-bit). Applications terminate abnormally when the ulimit data segment size is too small. Oracle recommends setting the data segment size to unlimited. See “Setting User Limits on 64-bit AIX” in the Oracle Enterprise Performance Management System Installation and Configuration Guide.

  • 13624319 -- HP-UX. Essbase Server running on HP-UX 11.23 is unable to create an application. Error messages:

    /usr/lib/hpux64/dld.so: Unsatisfied code symbol '__cxa_get_exception_ptr' in load module
    'EPM_ORACLE_HOME/products/Essbase/EssbaseServer/bin/libessasosm.so'.
    [Tue Jan 24 11:23:08 2012]Local/ESSBASE0///Error(1052003)
    Timed out reading from server
    [Tue Jan 24 11:23:08 2012]Local/ESSBASE0///Error(1054001)
    Cannot load application Apbg6641 with error number [1052003] - see server log file
    [Tue Jan 24 11:23:08 2012]Local/ESSBASE0///Error(1054067)
    Internal error

    Workaround: HP-UX 11.23 is not a supported operating system. For a supported version of HP-UX, see the Oracle Hyperion Enterprise Performance Management System Certification Matrix (http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html).

  • 13847733 -- Upgrade. If you are upgrading Essbase to a new machine, sample applications cannot be moved. New sample applications will be installed on the new machine.

  • 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 Oracle Hyperion Planning to synchronize Planning with Essbase and Essbase if the Delegated User Management option is enabled in Oracle Hyperion 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 Planning to synchronize Oracle Hyperion Planning with Oracle Hyperion Shared Services and Essbase if the Delegated User Management option is enabled and the user exists in more than one external repository.

  • 11800146, 10623580 -- Kernel. Direct I/O is not supported on Linux.

  • 10096616, 13084180 -- SSL. When SSL is enabled, some Essbase operations experience performance degradation.

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

  • 11725513, 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.

  • 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 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.

  • 20046936 -- To avoid abnormal application shutdowns, follow these recommendations:

    • Do not use the DELAYEDRECOVERY configuration setting in essbase.cfg, and in particular, do not set it to FALSE.

    • Do not run the MaxL statement alter database recover freespace.

Minimum Required Process Limits on Oracle Enterprise Linux 6

For a BI Shiphome installation of Essbase, on Oracle Enterprise Linux 6 (OEL6), you must set ulimit -u and ulimit -n to 4096 or higher. (14776250)

Support for the FRENCH_CANADA Locale

The FRENCH_CANADA locale is supported in Release 11.1.2.2.200.

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 Server (OPMN) service: EPM_epmsystem1.

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

    For example:

    Oracle HOME\instances\instance1\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.

    1. 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"/>
    2. 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 Server service (EPM_epmsystem1).

  9. Verify the following:

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

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

Copying an Aggregate Storage Application

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.100 documentation:

  • Minimum value: 1

  • 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.

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.

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.

To apply the AIX 5.3 kernel extensions update:

  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.

Authentication when Using SQL Interface with Microsoft SQL Server

When using SQL Interface with Microsoft SQL Server as a data source, only SQL Server Authentication (in which the SQL Server username and password is provided) is supported. Windows Authentication for SQL Server is not supported.

CLASSPATH Information

For diagnostic and informational purposes, Essbase prints the value of the CLASSPATH environment variable to the Agent console during JVM initialization.

Page File Sizes and NUMBLOCKSTOEXTEND Configuration Setting

Because of improvements to the way Essbase manages requests for additional disk space, the page file size may initially appear to grow faster for block storage databases. This is only a short term effect. Essbase allocates the needed memory in larger extensions instead of in several small increments.

When the Essbase block storage kernel updates a block, it writes to a new disk location. The block storage kernel searches free space to find a new disk location to use. If there is not enough free space to service the current request, the data file is extended.

The size of the extension is determined in part by a essbase.cfg setting, NUMBLOCKSTOEXTEND. The default size for this parameter is 2,048. The behavior in previous releases would approximate setting NUMBLOCKSTOEXTEND to a value of 1.

Configuration Setting for Running Essbase Server on Oracle Exalytics

When running Essbase Server on the Oracle Exalytics In-Memory machine, set the following configuration setting in the essbase.cfg file:

OracleHardwareAcceleration TRUE

The OracleHardwareAcceleration configuration setting applies to Exalytics only; it is not supported and should not be used in other deployments.

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.

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.

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.

Accessibility Considerations

It is our goal to make Oracle products, services, and supporting documentation accessible to the disabled community. Oracle's Oracle Essbase Spreadsheet Add-in supports accessibility features, which are described in Appendix E in the Oracle Essbase Spreadsheet Add-in User's Guide. The most up-to-date version of this guide can be found in the Oracle Enterprise Performance Management System Documentation Library on the Oracle Technology Network (http://www.oracle.com/technology/documentation/epm.html).

In addition, this Readme file is accessible in HTML format.