Skip to main content
Question

fme_data field converted to dateonly field, problem when writing to SDE


sijmensp
Contributor
Forum|alt.badge.img+3

I upgraded a workspace with a dynamic writer from FME 2022 to FME 2024. When inspecting the schema before writing there is fme_date and fme_datetime time fields. When writing to geodatabase it created dateonly fields from the fme_date fields when using FME 2024. When writing to SDE we get a ORA-210 / ORA-308 (invalid field type). What is the solution to this problem? I posted this before as addition to another forum topic. However someone from FME suggested to make a new topic. 

7 replies

ebygomm
Influencer
Forum|alt.badge.img+39
  • Influencer
  • June 2, 2025

What version of SDE are you running?

Are you trying to update an existing feature class or create a new feature class?


sijmensp
Contributor
Forum|alt.badge.img+3
  • Author
  • Contributor
  • June 2, 2025

The version of our ArcGIS geodatabase within Oracle is 10.8.1 according to our system administrator. We are writing data (DROP AND CREATE). 

 


nielsgerrits
VIP
Forum|alt.badge.img+55

I’m not sure which version SDE accepts date only fields, but I think it is newer than 10.8.1?

As a workaround, if you use a dynamic workflow, I would try to edit the schema feature to search and replace fme_date with fme_datetime.


ebygomm
Influencer
Forum|alt.badge.img+39
  • Influencer
  • June 2, 2025

So you don’t see any warning such as?

 


sijmensp
Contributor
Forum|alt.badge.img+3
  • Author
  • Contributor
  • June 3, 2025

Thanks for your responses. I'll try the workaround. I am directly writing into a lokal GDB using FME (which I do not get the warning, correct version) and then try to copy manually using ArcGIS Pro to the Oracle database on the older version. 


sijmensp
Contributor
Forum|alt.badge.img+3
  • Author
  • Contributor
  • June 19, 2025

11.2.0 is indeed required for the enterprise geodatabase version. Found out after contact with ESRI. Still working on the workaround. I'll update the topic when I got it to work. See Client and geodatabase compatibility—ArcGIS Pro | Documentation


sijmensp
Contributor
Forum|alt.badge.img+3
  • Author
  • Contributor
  • June 27, 2025

I made the following alterations to my script.

-in the schema for writing fme_date fields are converted to fme_datetime  to prevent writing dateonly fields to the portal enterprise geodatabase

-In the schema for writing fme_int64 fields are converted to fme_int32 to prevent writing bigints fields fields to the portal enterprise geodatabase. 

-Although I Implemented at first, it is not necessary to convert the values with only a data to a value with a date and time using the datetimeconverter

As this information could be useful to readers I added here in my topic. 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings