| We recently upgraded our FME Flow from version 2019 to FME 2025.2.1. Although we encountered several issues during the upgrade, the system is now running. However, we are facing a new error when executing an existing workbench. The workbench reads data from an Oracle table and generates GML and GeoJSON files. The files are generated successfully, but at the end of the process, the following error appears: Has anyone encountered this issue before? Any guidance would be appreciated. |
Solved
Error running FME workspace after FME flow upgrade to 2025.2.1
+2- Contributor
Best answer by j.botterill
Questions:
- I assume your Workbench (FME Form) is same version as Flow?
- Were you previously using 2019 FME in 32bit… or the now 64bit How to Setup an Oracle Instant Client for Use with FME – FME Support Center
- For the table you are reading, which version is the oracle database?
- Is that E drive path reachable from the latest Flow machine? You may need to check the environmental variables (for oracle “PATH” between old and new flow)
Compatibility:
Here is an article about compatibility between FME and Oracle RDBMS FME & Oracle Compatibility – FME Support Center
Workaround:
- You might be able to switch reader over to Oracle JDBC Driver format?
- Try to identify the problem features, using GeometryFilter to find arcs/ellipses and stroke them into lines… which geojson supports
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+57- Influencer
- Best Answer
Questions:
- I assume your Workbench (FME Form) is same version as Flow?
- Were you previously using 2019 FME in 32bit… or the now 64bit How to Setup an Oracle Instant Client for Use with FME – FME Support Center
- For the table you are reading, which version is the oracle database?
- Is that E drive path reachable from the latest Flow machine? You may need to check the environmental variables (for oracle “PATH” between old and new flow)
Compatibility:
Here is an article about compatibility between FME and Oracle RDBMS FME & Oracle Compatibility – FME Support Center
Workaround:
- You might be able to switch reader over to Oracle JDBC Driver format?
- Try to identify the problem features, using GeometryFilter to find arcs/ellipses and stroke them into lines… which geojson supports
+2- Contributor
Thank you,
It turns out this is a bug in FME 2025 FORM/FLOW. Safe has logged the issue and is currently working on a fix.
The GeometryPropertyExtractor and GeometryNameExtractor transformers are not detecting geometry correctly and are returning errors.
Additionally, the reader is unable to handle multiple geospatial columns, which is contributing to the problem.
+29- Safer
Hi
I wanted to provide an update.
A new build was released that includes a fix for this issue (FME 2025.2.4 Build 25835).
You can download it at: safe.com/downloads/