Overview

To authenticate with the repository database running on Oracle Autonomous Database, Essbase deployments on OCI use wallet files and the mTLS mode of encryption. Due to the recent changes in wallet files by Autonomous Database, Essbase instances running on OCI have an impact while connecting to the Autonomous Database.

If you have deployed Essbase on OCI via a Marketplace listing (versions prior to 21.4.2.0.0), and your deployment uses Autonomous Database as the repository database, you need to change how the Essbase instance connects to the repository database.

Impact on Essbase instances

This change impacts Essbase instances deployed from Marketplace listing versions prior to 21.4.2.0.0 that use Autonomous Database as the repository. Due to changes by DigiCert affecting TLS/SSL certificates in Autonomous Database wallet-based authentication, Essbase may not be able to connect to the repository database using the existing wallet file.

If impacted, the Essbase instance will not start. From AdminServer.out one of the following errors is seen:

ORA-12514 error
WARNING: Can not connect DB with URL jdbc:oracle:thin:@essxxxx_tp?TNS_ADMIN=/u01/config/domains/essbase_domain/config/wallets/wallet_xxx
java.sql.SQLRecoverableException: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
Couldn’t start admin server as tnslistener can’t be found
—-
ORA-29003 error
Attempt to connect to OCI failed. [ORA-29003: SSL transport detected mismatched server certificate.
Fatal Error : Server aborting
—-
ORA-28759 error:
When creating/importing application in Jet UI getting error ” Failed to create [<application_name>]. Reason: [Fatal Error: Server aborting]] “

Also, in essbase_server1.out below error is seen:

Error (1350014) Attempt to execute OCI statement failed. [ORA-28759: failure to open file]
Fatal Error : Server aborting

How to remediate the problem?

Download the new wallet files from the Autonomous Database that is used as the repository for Essbase, and follow the steps outlined in the Changes To Be Implemented In Essbase When Autonomous Databases Are Updated With New mTLS Libraries (Doc ID 2925030.1) per the listing version used to deploy Essbase on OCI.

Based on the listing version that was used to deploy, the location where the new wallet files need to placed vary. Also, once the new wallet file is downloaded, certain changes are required to the sqlnet.ora and tnsnames.ora files.

Where can I find additional information?

For more details on the changes in Autonomous Database, refer to the Action Required for Autonomous Databases (Doc ID 2911553.1)

For Essbase on OCI Marketplace deployment release notes, see: https://docs.oracle.com/en/database/other-databases/essbase/21/essop/oci-marketplace-deployment.html