Skip to main content
Solved

Error running FME workspace after FME flow upgrade to 2025.2.1

  • January 20, 2026
  • 2 replies
  • 89 views
suryakant1990
Contributor
Forum|alt.badge.img+2

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:

190  2026-1-20 14:33:00 | Router and Unexpected Input Remover (RoutingFactory): 
No geometry mapping entry found for 'fme_line' in metafile 
'E:\Server\fme\metafile\ORACLE_SPATIAL.fmf'. 
Please visit http://www.safe.com/support

Has anyone encountered this issue before? Any guidance would be appreciated.

  

Best answer by j.botterill

Questions:

  1. I assume your Workbench (FME Form) is same version as Flow?
  2. 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
  3. For the table you are reading, which version is the oracle database?
  4. 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:

  1. You might be able to switch reader over to Oracle JDBC Driver format?
  2. Try to identify the problem features, using GeometryFilter to find arcs/ellipses and stroke them into lines… which geojson supports

    2 replies

    j.botterill
    Influencer
    Forum|alt.badge.img+57
    • j.botterillInfluencer
    • Influencer
    • Best Answer
    • January 21, 2026

    Questions:

    1. I assume your Workbench (FME Form) is same version as Flow?
    2. 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
    3. For the table you are reading, which version is the oracle database?
    4. 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:

    1. You might be able to switch reader over to Oracle JDBC Driver format?
    2. Try to identify the problem features, using GeometryFilter to find arcs/ellipses and stroke them into lines… which geojson supports
      suryakant1990
      Contributor
      Forum|alt.badge.img+2
      • suryakant1990Contributor
      • Author
      • Contributor
      • January 30, 2026

      Thank you, ​@j.botterill , for your suggestions — they were extremely helpful in debugging this issue together with the Safe team.

      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.

        Community Stats

        32,413
        Posts
        122,925
        Replies
        40,132
        Members

        Latest FME

        Terms & ConditionsCookie settingsAccessibility statement
        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.