Skip to main content
Question

FME Flow - ORA-12154: TNS:could not resolve the connect identifier specified

  • May 8, 2025
  • 1 reply
  • 33 views

sarvani
Contributor
Forum|alt.badge.img+2

Hi All

Currently we are facing some weird issue

We have a FME workspace which is running fine in FME Form (2024.2.3 - 64 bit), we have published to FME Flow (2024.2.3) and when we ran the workspace from FME Flow, it started throwing below Ora error (changed ServerName & UserName values to XXX to hide)-

“ Error connecting to Oracle database: message was `ORA-12154: TNS:could not resolve the connect identifier specified'. (serverType=`ORACLE8I', serverName=`XXX', userName=`XXX', password=`***', dbname=`') “

I have cross verified the below from my side on FME Flow (Windows Server) and I’m not sure what I’m missing, please suggest how can I overcome this issue in FME Flow.

  1. We are not connecting to Oracle using local naming (tnsnames.ora file) instead using LDAP
  2. TNSPING ServiceName - resulted correct response 
  3. Ensured both Oracle Client 32 bit and Oracle Client 64 bit paths are part of ‘Path’ environment variable under system variables

FME Flow windows services (Application, Core, Database, Engines) are running with a service account, does service account needs any access at DB level or any folder where Oracle client is installed to understand that Oracle Identifier is already present ?

1 reply

hkingsbury
Celebrity
Forum|alt.badge.img+54
  • Celebrity
  • May 10, 2025

Initially this seems to me like it would be a networking issue, but you’ve ruled that out...

You say it works with Form, is that on the same machine? I also wonder if it might be a case of FME trying to use the 32bit driver. If you uninstall that (or remove it from the PATH) and restart FME Flow do you get the same issue?

EDIT: It may also depend on the order of the 32 and 64 paths in PATH. If you need them both, try switching the order around?


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings