Question

Issues writing to Oracle. Windows 2019/ FME Server 2021.2.5 Build 21816 - win64 Oracle 19C

jhawks
Rank
Badge +6

Workbenchs/ Connection String work fine on existing server. Moved them over to a new server and get:

 

ArcGIS Desktop 10.8.1 and Background georproccessing 64 installed, TNSNAMES is fine, can ping to oracle server.

 

822022-5-13 12:41:01 | Could not open the Enterprise Geodatabase. The error number from ArcObjects is: '-2147216028'. The error message from ArcObjects is: {No SDEHOME environment variable set}832022-5-13 12:41:01 | Please ensure the connection parameters are correct (server=`sde', instance=`sde:oracle$sde:oracle11g:ocspub', user=`encdirect', password=`***', database=`', version=`SDE.DEFAULT')

 

Edit: added SDEHOME Variable C:\\Program Files (x86)\\ArcGIS\\Desktop10.8\\bin

 

Still no good

 

FME Server 2021.2.5

Build 21816 - win64

3 replies

steveatsafe
Rank
Badge +11

Hi @jhawks​ 

You don't need SDEHOME to be configured for FME to work. That is likely a misleading error message from the ArcObjects side (but lets see if that holds true after some other information)

 

What other tests have you completed to 'isolate' the issue?

Can you TNSPING the Oracle Server with the 64bit Oracle Client?

If there are multiple bit version of Oracle Client, ensure the 64bit is first.

 

What type of Oracle Client do you have installed? Instant (recommended) or Full?

 

If you have downloaded the SQLPlus Client (for Instant Client) or have Oracle Full Client (included) can you test with the 64bit Oracle client that you can connect to the Oracle Database?

Do you have TNS_ADMIN environment variable configured? This will instruct all Oracle Clients (Full & Instant), and thus FME uses the single tnsnames.ora file for resolving the TNS Alias.

 

 

In FME, try publishing a workspace with an Oracle Reader and use the syntax host:port/servicename to connect to the Oracle Database - this will bypass the need for a valid tnsnames.ora and may help identify an issue with the tnsnames.ora file being used by the Oracle Client to resolve the alias (especially if there are multiple Full Oracle Clients installed).

 

Since ArcGIS Desktop is 32bit that won't be helpful as it will be using the Oracle 32bit Client if installed.

You could also isloate 64bit ArcObjects by using arcpy 64bit via geoprocessing to make a connection with the 64bit oracle client but that is likely more effort than necessary.

 

There shouldn't be a problem with the configuration you have using.

SteveatSafe
jhawks
Rank
Badge +6

Can TNSPIng, can connect thru SQL plus, only 64 bit oracle full client installed. Set TNSNAME to point to the TNSNAME.ORA File. Still no good.

 

Edit: Fixed! Had to reboot for patches, that likely applied environmental variables, all good now, thanks!

steveatsafe
Rank
Badge +11

Great! Yes either restarting FME Desktop or restarting the FME Server Engine service would be required. However, typically the engines restart often enough that this just happens.

I'm surprised you needed to reboot but maybe the engine restart was the key...

During my testing yesterday I didn't have to do that, just restarting the engine service is enough to pick up the new environment variable and path updates.

SteveatSafe

Reply


Community Stats

28,670
Posts
109,366
Replies
36,531
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.