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

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.

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

Iam the only one with this problems?

Hi ​@knigge,

Thanks for raising this! 

It was an intentional decision to set ‘Handle Multiple Spatial Columns’ to yes by default and to remove the option from the interface, so we’re always reading in all geometry columns. This decision was made to be consistent with our other database formats such as Microsoft SQL Server.

In order to know which geometry column you’re working with, you’ll need a GeometryRemover transformer, and it’ll allow you to choose which geometry column to remove. If you have three geometry columns, you may need a second GeometryRemover. 

I found this article really helpful to get acquainted with how to interact with the multiple geometry columns: Writing to Database Tables that contain Multiple Geometry Columns - 2026.1 and newer

I can see that being able to specify the Spatial Column in the reader parameters isn’t really ideal given that Handle Multiple Spatial Columns can’t be turned off. I’ll raise a problem report for our development team to see if we can prevent others from running into it. 

Update: I’ve filed a problem report for the 'Spatial Column’, tracked internally as (FMEENGINE-100142) and I’ll let you know as soon as it has been addressed.