Skip to main content
  • EN

Our app, on server 1, calls on a FME fmw file translation, also on server 1, and sends the data back to the user via the app. This was working perfectly up until ? time, I can't be sure exactly when it started as I only got the helpdesk issue routed to me yesterday. I did upgrade our Weblogic server on the same machine (server 1) last weekend but no other changes were made to the Oracle client or Java or anything other than Weblogic specific, but I'm not ruling out that it's not realted.

From server1, I can tnsping the database server, withing FME workbence the database connection test successful, running the fmw file from within the workbench connects successfully also, yet via the app I get the infamous ORA-12154: TNS: could not resolve the connect identifier specified.

I've played with the tnsnames.ora file modifying various items, setting IP as opposed to machine name, setting service_name as opposed to sid, etc....to no avail.

Any ideas?

How are you making the Oracle connection, using a database connection or with embedded connection properties?

If using a database connection, try to temporarily replace it with embedded connection properties, hardcoded into the workspace. It that works, it may be some issue with the app service user maybe not finding or having a corrupt internal database connection file.

Still failing with embedded parameters also, same error.

I jumped the gun on a previous post of log. Here is the log output and the database connection.

 

 

In the log you can see "Connecting to Oracle database 'fme_ro', but fme_ro is the user, not the database, the database is CVCPRI1. Not sure why FME doesn't see this from the database connection description shown below.

In the log you can see "Connecting to Oracle database 'fme_ro', but fme_ro is the user, not the database, the database is CVCPRI1. Not sure why FME doesn't see this from the database connection description shown below.

Showing results of database connection test

I don't believe the system is gaining access to the database connection file. The earlier fail with embedded parameters was actually working until the file hit the defined database connection part of the fmw file, then failing. So, my previous post of same error was correct, but not on the embedded parameters but later on the defined connection. I've tried deleting all connections and associated files and recreating but it still seems unaccessable.

How are you making the Oracle connection, using a database connection or with embedded connection properties?

If using a database connection, try to temporarily replace it with embedded connection properties, hardcoded into the workspace. It that works, it may be some issue with the app service user maybe not finding or having a corrupt internal database connection file.

Is there a way to ensure app service finds the file?

Found the issue. When I installed Weblogic, which our java app uses, I also installed a windows weblogic service that, by default installs and runs as local system account. By changing the service "Log On" to run under the admin account we use for all our maintenance and installations. the app was able to access the required files.....

Reply


Community Stats

30,159
Posts
114,480
Replies
37,806
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.