FME normally writes to Oracle Spatial Relational databases according to Oracle’s definition of the format. In this definition, user attributes for the layer <layerName> go into the table named <layerName>, and the geometry for a given feature is stored in one or more rows in the table named <layerName>_SDOGEOM.
Some GIS systems, such as Intergraph’s G/Technology, store user attributes in the <layerName>_SDOGEOM table in addition to the normal geometry definition. To accommodate such systems, the Oracle Spatial Relational writer can operate in an “Enhanced Relational” mode, which is triggered by setting the Oracle Spatial Relational writer’s Geometry Model parameter to a value of Enhanced Relational.
In the “Enhanced Relational” mode, each feature written is searched for attributes which match the names of the additional columns in the <layerName>_SDOGEOM table. Any matching attributes are written to their respective columns of the table, on every row used to define the geometry.
One complication when operating in the Enhanced Relational mode is that there may be an attribute in the <layerName>_SDOGEOM table that has the same name as an attribute in <layerName>’s user attribute table, but is to have a different value. To overcome this complication, the enhanced relational writer searches each feature for attributes named SDOGEOM.<attrName>; if found, each such attribute’s value is placed into the corresponding column <attrName> of the <layerName>_SDOGEOM table.