Skip to main content
Question

Error running translation: ORACLE Reader: 'Spatial Column' and 'Handle Multiple Spatial Columns' cannot be specified together since v2026.3

  • October 9, 2026
  • 2 replies
  • 14 views
knigge
Contributor
Forum|alt.badge.img+4

If I understand correctly, since the latest update, FME can include multiple geometry columns from an Oracle table in the workflow without much hassle.

Previously, it was necessary to manually set "Handle Multiple Spatial Columns" to Yes in the reader settings (if I remember correctly). Now, it seems that this option is set to Yes by default for readers, as my version of FME now loads all geometry columns without me having to configure anything. I also can't seem to find the option to enable or disable this anymore.

This is actually quite useful, but in my case, all geometry columns under User Attributes → Geometry Definition are greyed out, so I have no way to specify that I don't want to include all geometry columns.

When I try to specify which geometry column I want to use under Parameters → Spatial Column, I get the following error:

|ERROR |Error running translation: ORACLE Reader: 'Spatial Column' and 'Handle Multiple Spatial Columns' cannot be specified together

Am I just missing something, or is the option to disable reading multiple geometry columns no longer available in the new version?

Also, how can I tell which geometry column is being used by a transformer such as the AreaCalculator?

 

Kind regards,

2 replies

knigge
Contributor
Forum|alt.badge.img+4
  • kniggeContributor
  • Author
  • Contributor
  • October 9, 2026

As a result, areas are now being calculated incorrectly (at least, I suspect this is where the issue lies).

When I load a table in v2026.2, select the 2D geometry column, and calculate the areas based on it, I get exactly the same results as in QGIS. Opening the same workflow in v2026.3 also produces the correct results. However, in this case, the reader contains exactly one geometry column: the 2D column. This is because I'm opening a workflow created in v2026.2 in v2026.3, and in v2026.2, "Handle Multiple Spatial Columns" is set to No by default, so only that one column is available.

However, when I select the same table in v2026.3, all three geometry columns are loaded. When I then calculate the areas (using the same workflow originally created in v2026.2, but opened in v2026.3, with the table re-added using a new reader), approximately half of the records (out of more than 60 million) return an area value that is exactly double the expected value.

knigge
Contributor
Forum|alt.badge.img+4
  • kniggeContributor
  • Author
  • Contributor
  • October 9, 2026

The log also doesn't indicate which geometry column is actually being used (in v2026.3).

Community Stats

32,945
Posts
124,889
Replies
41,813
Members
Terms & ConditionsAccessibility 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.