Skip to main content
Question

Feature Writer to ORACLE_DATABASE warning for columns don't exist

  • July 1, 2026
  • 2 replies
  • 22 views
thesarge81an
Contributor
Forum|alt.badge.img+2

I am updating an existing table with a feature writer.

All data is well updated on all columns of my destination table.

 

However, I have a lot of warning telling me that the column xxxxxx does not exist in table XXXXXXX.

In the database, the columns exist, of course.

Connecting to ORACLE database `GRISS-RAC-SCAN.smartwork.br.it:1521/ORCLSW_SVIL' with user name of `DAFIF' and password of `***'
Connected to ORACLE database `GRISS-RAC-SCAN.smartwork.br.it:1521/ORCLSW_SVIL'
Oracle Writer: Going to Oracle Workspace `LIVE'...
Using existing column `GEOM' to store geometry in table `WPT'
Oracle table 'WPT' already exists. Using existing table
Column 'DISTANCE' does not exist in table 'WPT'
Column 'NAV_CTRY' does not exist in table 'WPT'
Column 'NAV_FLAG' does not exist in table 'WPT'
Column 'NAV_IDENT' does not exist in table 'WPT'

The same error is in different version of FME 2025.1 2026.2

I’ve read that another user had had the same error, and he resolved creating different features.
 

 

    2 replies

    j.botterill
    Influencer
    Forum|alt.badge.img+59
    • j.botterillInfluencer
    • Influencer
    • July 1, 2026

    No sure why the Unchanged port is being connected to UPDATE.WPT ?

    Sometimes your feature cache can become stale, and the schema isn’t presented to the feature writer. I suggest using Run entire workspace… or in 2026.1 or newer it should warn you if the cache is stale

     Green = good, Yellow = stale

    If you made changes to schema, be sure to open FeatureWriter - user attributes

    • if manual remove and re-import the destination table… 
    • simply toggle the automatic definition
    s.jager
    Influencer
    Forum|alt.badge.img+26
    • s.jagerInfluencer
    • Influencer
    • July 1, 2026

    Also: why FeatureWriters for Inserted and Updated (and Unchanged….), but a regular Writer for Deleted? Much simpler to use the fme_db_operation in a single FeatureWriter or Writer. Since you don’t do any processing after the ChangeDetector, that would be the most elegant option in my opinion.

    Secondly: What are your settings for Original Attributes to Preserve?

    Lastly: It’s not a good idea to post your fully qualified database name, nor is it necessary…

     

    Sometimes your feature cache can become stale

    Why I never use feature caching...

      Community Stats

      32,693
      Posts
      124,057
      Replies
      41,150
      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.