Oracle Essbase Patch Update: 21.8.1.0.0

Known Issues for Essbase 21.8.1.0.0

DigiCert will stop trusting G1 root certificates

DigiCert will stop trusting G1 root certificates (including TLS/SSL end-entity certificates) on April 15, 2026, per their announcement. This change may impact connectivity to Oracle Autonomous AI Database Serverless (ADB-S) for customers using mutual TLS (mTLS) authentication. Check the following steps – Urgent Action Required for Essbase on OCI Marketplace

(39015054)

Rollback Results in EAS Managed App Errors in Web Interface 

After rolling back from Essbase Release 21.8.x to an earlier version, applications that are ‘Managed by Essbase Administration Services’ (EAS Lite) may have the following issues. a) the ‘Managed by Essbase Administration Services’ tag is not applied, or b) the applications do not appear in the Essbase Web Interface, and the following error is logged: {{Failed to perform decryption using Advanced encryption standard (AES) algorithm.}} 

(38732061, 38856672)

Editing Outlines with Large Hierarchies

While editing an outline with large hierarchies using the Essbase web interface, you may experience performance issues.
(37068786)

Outline Updates through REST API are Case Sensitive

Batch outline updates may fail with Essbase platform log errors such as:

Cannot deserialize value of type ‘<type>’ from String “<string>”: not one of the values accepted for Enum class: [<list>].

This error occurs because dimension and member property names submitted during batch outline updates become case sensitive after application of required patches.

Workaround: Use lower case for batch outline editing property names, when posting dimAdd or mbrUpdate actions in the Run Batch Outline Edit REST API endpoint. For example, specify the Account dimension type as “account” rather than as “ACCOUNT”.

(37936531)

Patch Conflict with 21.7 and January 2025 CPU Patches

Applying the January 2025 CPU Patch when the 21.7 Patch is already applied, or applying the 21.7 Patch after the January 2025 CPU Patch is applied, results in a patch conflict.

The solution is to first apply the 21.7.1 Patch, and then the January 2025 CPU Patch.

If Oracle Essbase 21.7.0.0.0 Patch (Patch ID: 36675325) has been applied, you need to complete the following steps to apply the January 2025 CPU Patch:

1. Rollback Oracle Essbase 21.7.0.0.0. For more information, see Patch and Restore
2. Apply Oracle Essbase 21.7.1.0.0 Patch (Patch ID: 37418271).
3. Apply the FMW January 2025 CPU Patch. See Release 21.7.1.0.0 – February 2025 – Independent Deployment.

(37578313) 

Essbase 21.7.0.0.0 Rollback Deletes Sample Files

If a user rolls back Oracle Essbase 21.7.0.0.0, then gallery files will be missing. To avoid deleting gallery files, please run below script before applying Essbase 21.7 patch rollback:

For Linux:

• Download esb_patch_rollback_fix_linuxamd64.sh from My Oracle Support, patch id 37404647 – RELEASE UPDATE: ORACLE ESSBASE 21.7.0.0.0 ROLLBACK SCRIPTS
• Navigate to $ORACLE_HOME/.patch_storage/36675325*
• Copy esb_patch_rollback_fix_linuxamd64.sh to $ORACLE_HOME/.patch_storage/36675325*
• Execute esb_patch_rollback_fix_linuxamd64.sh
• sh esb_patch_rollback_fix_linuxamd64.sh
• Rollback 21.7

For Windows:

• Download esb_patch_rollback_fix_winamd64.zip from My Oracle Support, patch id 37404647 – RELEASE UPDATE: ORACLE ESSBASE 21.7.0.0.0 ROLLBACK SCRIPTS
• Unzip esb_patch_rollback_fix_winamd64.zip to get esb_patch_rollback_fix_winamd64.cmd
• Navigate to $ORACLE_HOME/.patch_storage/36675325*
• Copy esb_patch_rollback_fix_winamd64.cmd to $ORACLE_HOME/.patch_storage/36675325*
• Run esb_patch_rollback_fix_winamd64.cmd
• Rollback 21.7

(36925645)

Data Load and Dimension Build Can Return a Warning

Creating a local connection using CLI createlocalconnection command and then running a streaming data load  or dimension build as system administrator or power user can return SLF4J warnings, such as:

SLF4J: Failed to load class “org.slf4j.impl.StaticLoggerBinder”.

SLF4J: Defaulting to no-operation (NOP) logger implementation

SLF4J: See “http://www.slf4j.org/codes.html#StaticLoggerBinder” for further details.

Drillthrough IN clause limit set to 1000

(36659416)

Creating Federated Partition from ASO Cube can Incorrectly Select Formula Members

When creating a federated partition from an ASO cube using the Federated Partition wizard in Cube Designer, the wizard may incorrectly select formula members. Deselect these. Only stored members should be selected.

(36544452)

Essbase 21.5.5.0.0 Rollback Deletes Sample Files

If a user rolls back Oracle Essbase 21.5.5.0.0, then there will be two Essbase sample files that will be missing:

• orahome/essbase/products/Essbase/cubedesigner/Cubes/Technical/Drill Through/DrillthroughDS.csv
• orahome/essbase/products/Essbase/cubedesigner/Cubes/Applications/Demo Samples/Aggregate Storage/ASO_Sample_Data.txt

Further, if a user upgrades this same environment via 21.6 opatch, ASO_SAMPLE_DATA.TXT AND DRILLTHROUGHDS.CSV files will still be missing.

(36515157, 36620471)

Floating-Point Differences Starting with Essbase 21.5.5.0.0 Release Update Revision for Windows

Starting with Essbase 21.5.5.0.0, Visual Studio C++ has been updated to 2022. There are cases where certain floating-point operations results have changed due to this upgrade.

(36360152)

Closing the Web Browser Tab During a Data Load Leaves a TMP Directory

When performing a data load using a load rule and a large data file in the Essbase web interface, if you close the browser tab or window while the load is in progress, a TMP directory is created.

The directory is created in the user directory on the Essbase file catalog, where “user” means the Essbase user who performed the data load. You can find the user directory using the file catalog in the Essbase web interface, or you can find it on the Essbase server machine under <Application Directory>/catalog/users/<username>.

The directory format is, __TMP__<currenttimestamp>__LOCAL (For example, __TMP__1698299191774815__LOCAL). The directory contains the data, load rules, and other files.

Workaround:

You can optionally delete the TMP folder by following these steps:

1. In the Essbase web interface, navigate to Files > Users > <username>.

2. Click the Actions menu to the right of the __TMP__<currenttimestamp>__LOCAL directory and click Delete.

Note:

Deleting the TMP directory is optional as it will not have any adverse effect on UI operations, but it is recommended to do so.

(36119888)

 Certification Authority (CA) Signed Certificates are Being Updated

Certification Authority (CA) signed certificates are being updated after replacing 21.3 CA-signed certificates with the new TLS tool, on the patched 21.4 environment.

Workaround: For Windows, all open files and folders must be closed before replacing CA-signed certificated with the TLS tool, after 21.4 patching.

(34113185)

Existing Essbase Marketplace Customers Unable to Create or Import an App (applies only to Listing versions 21.4.0.0.1 and earlier)

For existing Essbase Marketplace versions 21.4.0.0.1 and earlier only, unable to create or import an app on the Essbase database side, receive a fatal error that the server is aborting.

Workaround: Refer to KM Document “Changes To Be Implemented In Essbase When Autonomous Databases Are Updated With New mTLS Libraries (Doc ID 2925030.1)”.

(35007569)

On Windows, Cannot Replace or Edit Partitions When Using Localhost

On Windows, a user cannot replace or edit Partitions when using localhost when a Partition is first created.

Workaround: Use host:port or the agent URL instead of localhost.

(34325649)

 Essbase Web Interface does not Show or List Database

Essbase Web Interface does not show or list databases after clicking on the expand Application button on Windows when the Operating System is set to a language other than English. Current REST and Web Interface works in co-ordination only when server language is en and for client side user can change required language in browser.

Workaround: set -Duser.language=en in weblogic server <Domain home>/bin/setDomainEnv.sh

(34098716)

Cluster Entries Still Present in HSS after Uninstalled

EssbaseCluster entries are still present in HSS after an uninstall. Manual steps to cleanup EPM registry:

1. List the components with type ‘CLUSTER’

<EPM_ORACLE_INSTANCE>/bin/epmsys_registry.sh view CLUSTER

2. Select the ID of CLUSTER with your essbase cluster name (eg.’EssbaseCluster-1′) and ID’s of its children’s.

a. Delete the components with those ID’s.
<EPM_ORACLE_INSTANCE>/bin/epmsys_registry.sh deletecomponent \#componentID
b. For every child component of type ‘APPLICATION’ remove the corresponding file by replacing extension ‘.ESB’ or ‘.ESBAPP’ with ‘.instance’ in ID. For example
– Child ID: ‘Analytic Servers:EssbaseCluster-1:1.ESB’ and TYPE: APPLICATION <EPM_ORACLE_INSTANCE>/bin/epmsys_registry.sh removefile SYSTEM9/ESSBASE_PRODUCT/@’Analytic Servers:EssbaseCluster-1:1.instance’
– Child ID: ‘Sample_EssbaseCluster-1_1.ESBAPP’ and TYPE: APPLICATION <EPM_ORACLE_INSTANCE>/bin/epmsys_registry.sh removefile SYSTEM9/ESSBASE_PRODUCT/@’Sample_EssbaseCluster-1_1.instance’

3. List the components with type ‘PROJECT’, select the ID of PROJECT with your essbase cluster name (eg. ‘EssbaseCluster-1’) and delete that component.

<EPM_ORACLE_INSTANCE>/bin/epmsys_registry.sh view PROJECT
<EPM_ORACLE_INSTANCE>/bin/epmsys_registry.sh deletecomponent \#componentID

4. List the components with type ‘PROVIDER_SERVICES_WEB_APP’, select the ID of component with ‘instance_home’, ‘localhost_name’ that matches with your essbase instance and delete that component.

<EPM_ORACLE_INSTANCE>/bin/epmsys_registry.sh view PROVIDER_SERVICES_WEB_APP
<EPM_ORACLE_INSTANCE>/bin/epmsys_registry.sh deletecomponent \#componentID

5. If EAS is configured, then list the components with type ‘ADMIN_SERVICES_WEB_APP’, select the ID of component with ‘instance_home’, ‘localhost_name’ that matches with your essbase instance and delete that component.

<EPM_ORACLE_INSTANCE>/bin/epmsys_registry.sh view ADMIN_SERVICES_WEB_APP
<EPM_ORACLE_INSTANCE>/bin/epmsys_registry.sh deletecomponent \#componentID

(33023854)

LCM Imports can Loop Interminably

LCM imports of 21.3 or later zip files will occasionally loop interminably after uploading the zip file if there is a sub directory inside catalog/users/<username>.

(34177103)

Error Message Displayed When a Shared Member Occurs Before a Stored Member

In the Essbase web interface, when a shared member occurs before a stored member in an outline, an error message is displayed. Currently the message shows only in edit mode.

(34413552)

In Failover Transition Period May Encounter Errors

While in Failover transition period, a user may encounter errors if user attempts to connect. Errors vary depending on the operations during the transition period for failover.

Examples of errors from Smart View:

• Cannot set cube view properties. Essbase Error(1290001): Network Error [10061]: Unable To Connect To [<host_URL>:30770:secure]. The client timed out waiting to connect to the Essbase Server using TCP/IP. Check the network connections. Also make sure that Server and Port values are correct.
• The client timed out waiting to connect to Essbase Agent. Check your network connections, host and port values, and that Essbase is started

Examples of error from Maxl:

• ERROR – 103 – Unexpected Essbase error 1030818.
• ERROR – 1040025 – Invalid platform [16707]. An application protocol error might exist between server and client processes.
• ERROR – 1040065 – Protocol mismatch may occur if a client other than an Essbase Client tries to access Essbase or if the packet is corrupted.
• ERROR – 1030818 – The client timed out waiting to connect to Essbase Agent. Check your network connections, host and port values, and that Essbase is started.
• ERROR – 103 – Unexpected Essbase error 1040059.
• ERROR – 1040059 – Failure while getting the active Essbase node for cluster [<host_URL>:4443/essbase/agent]. Runtime Provider Services
• Error: [EssbaseCluster;agent.runtime.find.by.id.failed [essbase_cluster]].

Example of an error from Essbase Web Interface:

• Essbase Error(1042006): Network error [10061]: Failed to connect to [<host_URL>:6423:secure]”

Workaround: On clients Essbase Web Interface, Maxl or SmartView disconnect then re-connect, to get past the error messages.

(34424813)

On Linux 8, import and create new application is failing with a network error.

Workaround: Update the Essbase.cfg for crashdump location.

(34410315)

Create Partitions on Rollback

A roll back from Oracle Essbase 21.3.2.0.0 RUR to an earlier release will require users to recreate all partitions and partition behavior will be as it was in the earlier release.

(34014721)

Partition User Connections are not Cleared

In some cases, a partition user’s connections are not cleared after the user disconnects from a target cube in Smart View Client.

Workaround: Use disconnect all to shut down all connections.

(33989240)

 Rollback to Essbase 21.2 RU if 21.2.1 or 21.2.2 RUR has been applied

If either the 21.2.1.0.0 Release Update Revision (Patch 32957244) or 21.2.2.0.0 Release Update Revision (Patch 33387697) was applied, then you will need to roll back to Essbase 21.2 Release Update (Patch 32957244) before applying the Essbase 21.3 Release Update patch.

(33671620)

Running a CLI Script can Return an Error

When running a CLI script can return the following error:

FAILED TO READ USER INFO FROM ‘/HOME/<user_directory>/.ESSCS/.CLI’

Workaround: Set this variable on the same terminal before running a CLI script:

export ESSCLI_CACHE_DIR=/scratch/cli

(32699417)

Unable to Login from Essbase Administration Services Web Console after Opatch Rollback

A user is unable to login from Essbase Administration Services Web Console after rolling back a 21C opatch and an error is returned:

Could not connect Administration Server <servername>.Client and server are different versions. Client version is 21.2.0.

Workaround:

1. Clear java cache and re-launch the url and login
2. In Windows, run ‘javaws -viewer’
3. In the application remove all easconsole.jnlp files, download the easconsole.jnlp again and run it.

(33012934)

Logging in using Maxl or Essbase Administration Services can Fail

Logging in using Maxl or Essbase Administration Services can fail when using the second SSL Essbase Server using host:port:secure format.

With Essbase Administration Services an error is returned when trying to add a second essbase server with host:port and user SSL enabled:

• Error: 103: Unexpected Essbase error 1030818
• Error: 1040142: NZERROR: nzos_Handshake failed(29024)
• Error: 1042006: Network error [0]: Failed to connect to [<host_name>:<port>]
• Error: 1030818: The client timed out waiting to connect to Essbase Agent. Check your network connections, host and port values, and that Essbase is started.

With MAXL an error message is returned after this call is entered:

MAXL> login admin password on <host_name>:<port>:secure;
ERROR – 103 – Unexpected Essbase error 1030818.
ERROR – 1040142 – NZERROR: nzos_Handshake failed(29024).
ERROR – 1042006 – Network error [0]: Failed to connect to [<host_name>:<port>].
ERROR – 1030818 – The client timed out waiting to connect to Essbase Agent. Check your network connections, host and port values, and that Essbase is started..

Workaround: Use CAPI URL.

(33017161)

Unable to launch the Essbase Web Interface and Essbase Administration Services Console on Firefox

After replacing a CA signed certificate, users are unable to launch the Essbase Web Interface and Essbase Administration Services on Firefox.

Workaround: Use a different browser than Firefox.

(33218323)

Status of Essbase Service Does Not Show as Running

After installation and configuration Essbase processes are running but were not started by Windows Essbase service. Thus, the status is not going to be reflected in the service control. To start as a service, process should be stopped and service should be started.

(33333640)

GL Allocation using MDX Insert Fails on Windows Platform

GL Allocation using MDX Insert fails on the Windows platform when utf8 is enabled and CUSTOMCALCANDALLOCTHRUINSERT and FORCECUSTOMALLOCTHRUINSERT are set to TRUE

(33397525)

Data Retrieval Fails with Telapi 16.2 Drivers

Data retrieval fails when using Telapi 16.2 Drivers and returns an error:

TPTapi failed to connect to Teradata database with error message [TPTAPI_INFRA: API306: Error: Conflicting data length for column(3) – SKU. Source column’s data length is (15) Target column’s data length is (30).]

(33504426)

FMW July 2021 CPU Patch Fails

The FMW July 2021 CPU patch fails when applied to Oracle Essbase 21.3 with Teradata Client is installed.

Workaround: Uninstall the Teradata Client.

(33501070)

 Error when installing Cube Designer

In some cases, an error is returned when trying to install Cube Designer via SmartView Client:

Parsing manifest.svextsetup of installer failed.

Workaround: Download the Cube Designer installer from the Essbase Web Interface and install locally.

(32435554)

Hierarchy Viewer in Cube Designer can only display Excel Text or Excel General formatted cells

The Hierarchy Viewer in Cube Designer can only display Excel Text or Excel General formatted cells correctly. For example, if a cell is formatted as Date format the Hierarchy Viewer will display the date value, not the date text.

Workaround: If a user has date formatted cells, they can build the cube using the date cells and then export the cube into another Excel workbook. The exported workbook will no longer have the date formats (now in General Format) and will show up correctly in the Hierarchy Viewer.

(32008795)

Scroll Bar is Hidden

The scroll bar is hidden by the options in the console or the textbox in the Outline when using Safari Version 14.0.

(32603415)

Menu is not opaque

When using Safari Version 14.0, when the menu is selected for any application and is expanded, the hamburger icon can still be seen. The menu is not completely opaque as expected.

(32513628)

Users created in Web Interface disappear after Oracle Essbase is restarted

Users created in Web Interface disappear after Oracle Essbase is restarted.

Workaround: Enable “Master first” setting in Embedded LDAP settings in Weblogic console. This will ensure users/groups are always created in the master copy.

(32438058)

Application Log Not Including All Nodes

When you use Essbase Web Interface to download the application log, it does not show activity for the other nodes in the failover cluster.

(32201385)

REST Request can fail

REST Requests can fail with 403 response in some cases when using a TLS/secure configuration with the October FMW CPU patch.

Workaround: Restart the server.

(32170842)

With SSL-enabled failover, dimension build or dataload can fail

With SSL-enabled failover environment, running a dimension build or dataload with an existing rules file from the Web Interface against a data source can fail and return errors:

Query post for the REST data source failed with error []
NZERROR: nzos_Write failed(28862)

Workaround: Users need to manually update the URL in the rules files if they are using data source for dim build and data load to add the correct scheme and host port.

(31841679)

With SSL-enabled failover and using “Oracle HTTP 12.2.1.4”  Server can fail

With SSL-enabled failover and using “Oracle HTTP 12.2.1.4” can fail under a heavy load.

(31928860)

Export via Migration Utility can fail

If Essbase is configured to use self-signed certification and TLS, the certificate should be imported to the java class store that is used to call the Migration Utility.

(31778251)

Data load or dimension build can fail

When keep-alive is enabled, Data load or dimension build using Oracle Database as a data source from Web Interface can fail with error:

Query post for the REST data source failed with error []

Workaround: Disable keep-alive.

(31767457)

Error when system has Essbase using the same port

When multiple Essbase servers are running on the same port on standby node and a failover occurs, an error can be returned

Network error [10061]: Failed to connect to [<machine>:secure]

and a user will be unable to retrieve an application list, the list will be empty.

Workaround: Users should ensure Essbase port is free and available in all the nodes. It will be bound only when the node becomes active. In case port binding fails at a later stage when a passive node becomes active, then customer should update the new port in essbase.cfg and restart that node. Clients require re-login after this.

(31947481)

Drill Through Reports are not displayed in the Web Interface

Drill through reports created in 11.1.2.4 Essbase applications are not displaying in 21.1 Essbase Web Interface after migrating Essbase applications from 11.1.2.4 to 21C.

(32006962)

Managed Server fails to start when starting on a different machine

If you configure an Essbase domain with secure mode on and use no listen addresses and start the admin server, then start a managed server the managed server fails.

(32125053)

Configuration of products can take excessive time at “Start Weblogic” stage and return an error

Configuration of products can take excessive time at “Start Weblogic” stage when EAS listen address is set to some other host name with non-default SSL ports with error messages returned:

Logging configuration class “oracle.core.ojdl.logging.LoggingConfiguration” failed oracle.core.ojdl.logging.LoggingConfigurationException: ODL-52051: unable to process file ‘null/logging.xml’; exception: java.io.FileNotFoundException: <path>/OP96/Middleware/Oracle_Home/essbase/lib/null/logging.xml
(No such file or directory)

Workaround: The EAS listen address should be set to localhost.

(31896182)

Data Load Failed When Links Added at OS Level

If you add links at the OS level, and you upgrade your system, a data load error may occur.

For example, if one or more of the following files don’t exist in /usr/lib:/usr/lib64/libgssapi_krb5.so:

• /usr/lib64/libkrb5.so:
• /usr/lib64/libk5crypto.so:
• /usr/lib64/libkrb5support.so

but a specific version of these files exist, you must create a soft link as root, or, run sudo command and create soft link between /usr/lib64/<library> and /usr/lib64/<library>.<version>.

For example:

sudo ln -s /usr/bin/libgssapi_krb5.so.2 /usr/bin/libgssapi_krb5.so

(31435739)

EAS managed application should not be modified for new 21C features

EAS managed applications should not be modified for new 21C features through any of the Essbase 21C interfaces (for example Web Interface, REST API, Java API).

(31892640)

Creating an aggregate storage application in the Web Interface and then enabling EAS management can result in unexpected issues

Creating an aggregate storage application in the Web Interface and then enabling EAS management can result in unexpected issues. For example, edit the application in EAS edit mode and set solve order to a value for the Time Dimension and save the outline. Then use the Web Interface to open the same outline, and notice that all descendant members have this new solve order. On the other hand, if you start from Web Interface to set the solve order for the Time Dimension, it only changes the solve order for the Time Dimension and not the descendant members.

(31908376)

EAS Console installation can fail

When installing EAS Console 21.1 on top of an EAS Console 11.1.2.4 installation can fail and return the following error:

ERROR 1316 THE SPECIFIED ACCOUNT ALREADY EXISTS

Workaround: Uninstall 11.1.2.4 EAS Console before installing EAS Console 21.1.

(31941471)

Must close browser and re-launch when an error is encountered

With TLS-enabled failover, transaction periods take longer and can result in an error being returned:

Failed to connect to [<IP>:6423:secure]” error on UI, users MUST close current browser and re-launch new browser to see app list retrieve. Add new tab or clear cache still see error and app list is empty.

Workaround: When encountering this error message, close your browser and re-launch the browser.

(31962758)

Some database settings are not getting upgraded from Essbase 11.1.2.4 to 21.1

Some database settings are not getting upgraded when migrating from Essbase 11.1.2.4 to 21.1 after the 11.1.2.4 application is imported using CLI:

• Database level data_cache_size
• data_file_cache_size
• Index_cache_size
• Index page setting (KB)
• Index page current value
• compression zlib; – This option is not available to verify in Web Interface
• calc_string ‘CALC DIM(Year, Measures, Product);’;
• Database note
• Performance statistics settings

(32033983)

Some settings are not getting upgraded from Essbase 11.1.2.4 to 21.1

Some settings are not getting upgraded when migrating from Essbase 11.1.2.4 to 21.1 after the 11.1.2.4 application is imported using CLI:

• App Level Cache Size
• Max Attachment File Size
• Message_Level Settings

Workaround: After import, it is recommended that you review the settings and change them as needed in 21.1.

(32033987)

Creating an app can fail if gcc-cc+ package is not installed

Creating an app from the Web Interface, MaxL, or EAS can fail with the following error messages being returned:

In the essbase_server1.out log following exception is seen –

Error (1021090) Can not load EssOCI shared library [libessoci.so], OS status [No errors]. Make sure that the required binaries are present with correct environment variables set
Error (1350016) Unable to load OCI dll.
Fatal Error : Server aborting

This happens when libocci.so.12.1 is missing from the $ORACLE_HOME/lib directory, as it was not installed during installation due to absent gcc-c++ compiler.

Workaround: It can be installed by running yum install gcc-c++ as root user. Then the following commands can be run to install libocci.so.12.1:

>export ORACLE_HOME=<the Oracle Home path>
>$ORACLE_HOME/bin/genoccish

(32050637)

Data Audit Trail will not work when Essbase is configured with MSSQL

Data Audit Trail will not work when Essbase is configured with MSSQL.

(31886797)

Transaction replay based on sequence id fails

Transaction replay based on sequence id fails. For example, when running the following MaxL commands:

MAXL> query database “App”.”Db” list transactions;
MAXL> alter database “App”.”Db” replay transactions using sequence_id_range 1 to 2;

An error message is returned:

ERROR – 1056213 – message from server [Replaying a request that has an older start time [time_stamp], than the latest of last replayed request or the last restored backup’s time [time_stamp], is not allowed. You may only skip requests

(32070232)

Incorrect directory location is returned in error message

If an error is encountered during creation of the database schema, the error message returns the wrong directory location of the rcu.log:

Error message returned:

Encountered error: Execution is failed. Errors could be found in: /scratch/<GUID_Name>/temp/<essbase_config auto generated identifier>/rcu.log

Correct location of log is /scratch/<GUID_Name>/temp/<essbase_config auto generated identifier>/rcu/logs/rcu.log

(32103293)

TNS_ADMIN must be set on nodes

In order for a failover node to work, TNS_ADMIN must be located on each cluster node of the failover environment.

(32121344)