When Using TNS Alias Name, OCI Connection From Load Rule In EAS Fails With Error "EssOCI failed to connect to Oracle database with error message [ORA-12154: TNS:could not resolve the connect identifier specified" (Doc ID 2930905.1)

Last updated on JULY 31, 2024

Applies to:

Symptoms

Failed to establish connection to SQL Database Server error occurs when trying to connect to Oracle db from load rule using OCI connection from EAS Data Prep Editor's SQL Interface.

The issue happens when using a TNS alias in EAS Data Prep editor SQL interface when in the field "Oracle Call Interface (OCI) service name".

For example, if the the TNS alias name ORCL_ESSBASE has been added to tnsnames.ora following errors are found in the Essbase application log:

[<timestamp>]Local/<application name>/<database name>/<username>@Native Directory/3876/Info(1021097)
EssOCI is initializing the connection to Oracle database on server [ORCL_ESSBASE]

[<timestamp>]Local/<application name>/<database name>/<username>@Native Directory/3876/Info(1021099)
EssOCI failed to connect to Oracle database with error message [ORA-12154: TNS:could not resolve the connect identifier specified
]

[<timestamp>]Local/<application name>/<database name>/<username>@Native Directory/3876/Error(1021001)
Failed to Establish Connection With SQL Database Server. See log for more information

[<timestamp>]Local/<application name>/<database name>/<username>@Native Directory/3876/Warning(1080014)
Transaction [ 0x180001( 0x636a9467.0xbfe50 ) ] aborted due to status [1021001].

Cause

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