Connectivity May Fail for Load Rule Using Oracle Call Interface (OCI)

On Windows, previewing data or running a dimension build or data load with a rule file that uses Oracle Call Interface (OCI) connection strings may fail with the following error message:

Attempt to connect to OCI failed. [ORA-12638: Credential retrieval failed].

The cause of this issue is that the version 19c Oracle Database server and the 19c client (in this case the client is where Essbase is installed) has no setting, or has the following setting in sqlnet.ora: SQLNET.AUTHENTICATION_SERVICES=(NTS)

The solution is to set SQLNET.AUTHENTICATION_SERVICES=(NONE) in sqlnet.ora on the computer where Essbase is installed.

  1. In <Oracle Home>/network/admin, locate sqlnet.ora
  2. Open the file and add SQLNET.AUTHENTICATION_SERVICES=(NONE)
  3. Restart the Essbase application.

Note:

If the sqlnet.ora file does not exist, create it by adding a text file with the name sqlnet.ora.

The parameter may be in tnsnames.ora instead of sqlnet.ora. Refer to usage notes in the SQLNET.AUTHENTICATION_SERVICES documentation for Oracle Database 19c.