Essbase 21c On-Premise: Essbase Applications Fails To Start With Error: [Failed to start [<application name>]. Reason: [Fatal Error : Server aborting]] (Doc ID 2930900.1)

Last updated on MARCH 01, 2023

Applies to:

Symptoms

After adding parameter in sqlnet.ora for the Essbase repository database, Essbase Server can be started, but Essbase applications can not be started.
SQLNET.ALLOW_WEAK_CRYPTO_CLIENTS = FALSE

Following error is shown in the Essbase web UI when attempting to start an application:

Error:
[Failed to start [<application name>]. Reason: [Fatal Error : Server aborting]]

Following error is shown in essbase_server1.out:

[<timestamp>] (null) / Error (1350014)
Attempt to execute OCI statement failed. [ORA-12160: TNS:internal error: Bad error number
]

Fatal Error : Server aborting

If parameter SQLNET.ALLOW_WEAK_CRYPTO_CLIENTS = FALSE it fails. If parameter SQLNET.ALLOW_WEAK_CRYPTO_CLIENTS = TRUE, or commented out, applications can be started.

Changes

 Following parameters were added to sqlnet.ora for the Essbase repository database due to company security requirements. These settings activates Oracle Native Network Encryption (NNE).

SQLNET.ENCRYPTION_SERVER = REQUIRED
SQLNET.ENCRYPTION_TYPES_SERVER = (AES256)
SQLNET.CRYPTO_CHECKSUM_SERVER = REQUIRED
SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER = (SHA512)
SQLNET.ALLOW_WEAK_CRYPTO_CLIENTS = FALSE

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.