My Oracle Support Banner

Essbase Unable To Connect To Oracle Database After Changed Encryption Settings (Doc ID 3000096.1)

Last updated on JANUARY 29, 2024

Applies to:

Hyperion Essbase - Version 21.3.2.0.0 and later
Information in this document applies to any platform.

Symptoms

The Oracle database used for dimension build and dataload have changed encryption settings and Essbase can no longer connect.

Example settings in database sqlnet.ora:

Old settings
 SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER = (SHA256,SHA1)
 SQLNET.CRYPTO_CHECKSUM_TYPES_CLIENT = (SHA256,SHA1)

New Settings
 SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER = (SHA512,SHA256)
 SQLNET.CRYPTO_CHECKSUM_TYPES_CLIENT = (SHA512,SHA256)

After making the changes to sqlnet.ora, Essbase  is failing to connect to the Oracle database with following error:
OK/INFO - 1350007 - Creating connection pool of size [1] for connection string [DSN=<dsn name>;UID=....;PWD=....].
  ERROR - 1350005 - Attempt to connect to database failed with error [[Oracle DataDirect][ODBC Oracle Wire Protocol driver][Oracle]ORA-12650: No common encryption or data integrity algorithm].
  ERROR - 1241101 - Unexpected Essbase error 1350005.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


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