Skip to main content
Question

ArcSDEQuerier - database client sofware failed to load

  • December 6, 2024
  • 3 replies
  • 39 views

timboberoosky
Contributor
Forum|alt.badge.img+6

I authored some scripts years ago that use the ArcSDEQuerier transformer to query for records in a versioned 10.1 ArcSDE Geodatabase. The machine that FME resides on has FME 2019.3.1, both ArcGIS 10.1 and ArcSDE 10.1, and both Oracle 32-bit (ArcGIS) and 64-bit (ArcSDE) clients installed. The scripts have worked for years without issue. Recently, I’ve had to modify them a bit and on a development FME machine, the ArcSDEQuerier transformer works fine, but promoting them to another same-build FME machine has had some odd results. If I use the exact scripts/workspaces from the dev machine, the ArcSDEQuerier throws the error seen below. Or if I open scripts that were already on this machine, untouched, the ArcSDEQuerier also throws the same error:

 

However sometimes, and I stress sometimes, if I open a brand new workspace and add a single ArcSDEQuerier, I can connect to the same DB using the same credentials without issue:

 

I know the obvious answer is that something has changed with ArcSDE, or Oracle, or something else on this machine. However I don’t understand why it works sometimes and not others.

Any thoughts from anyone on what to look into?

3 replies

hkingsbury
Celebrity
Forum|alt.badge.img+54
  • Celebrity
  • December 9, 2024

Prefacing with 2019 and 10.1 both being well out of support….

What is your reasoning for using an ArcSDEQuerier? It has been depreciated in newer versions of FME.

What happens if you use a (feature) Reader/Writer instead, or even an SQLExecutor? Do you get the same issue?


timboberoosky
Contributor
Forum|alt.badge.img+6
  • Author
  • Contributor
  • December 10, 2024
hkingsbury wrote:

Prefacing with 2019 and 10.1 both being well out of support….

What is your reasoning for using an ArcSDEQuerier? It has been depreciated in newer versions of FME.

What happens if you use a (feature) Reader/Writer instead, or even an SQLExecutor? Do you get the same issue?

 

I should have mentioned, I did update the workspaces to use FeatureReaders instead of  ArcSDEQueriers, and these work as I’d expect.

This was more of a nice-to-know type of question where I can’t think of, or see, anything different on the machine now that could have caused this. And if anyone else had experienced this before, it would be helpful to try to explain.


nielsgerrits
VIP
Forum|alt.badge.img+54

I found a related question, but no answer…

Not really FME related, just an observation. When we have issues where it is hard to reproduce the error due to inconsistent behaviour, it often has something to do with load balancing, multiple machines sharing tasks and a configuration mismatch between the different machines. So when we see these kind of symptoms, we first make sure load balancing is taken out of the equeation if possible. The symptoms you describe alert my loadbalancer nerves :)


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