Skip to main content

I’ve come across an issue a couple times where the Oracle writer appears to go stale after a few months of working fine. Has anyone else come across this issue and do you have a better fix than mine?

Problem: I run an FME workbench that writes data to Oracle, the workbench completes successfully and the log file tells me fme_features were written. When I go look in Oracle to confirm the deltas, the records were not changed.

Current fix: If I replace the Oracle Writer and re-run the workbench then the records in Oracle do get changed.

 

Any help would be appreciated

Are you using a Writer or a Feature Writer with the Oracle format. The advantage of the workflow transformer Feature Writer is that there is a Summary port which will output the total_features_written

A screen shot of the Writer feature type parameters is always helpful. Is the Feature operation = INSERT and what about the “table handling”. https://docs.safe.com/fme/html/FME-Form-Documentation/FME-ReadersWriters/oracle_nonspatial/feature-types-w.htm

You may want to double check that the username in the Oracle (database connection / easy connect string) has indeed the permissions to commit edits

 


Maybe disabling ‘persistent connection’ helps, you can find that in the edit options of your writer.


Hey ​@j.botterill 

I am using an Oracle writer. I am using fme_db_operation as the Feature operation so it can handle INSERT, UPDATE, and DELETES, and I am using ‘Use Existing’. I guess I didn’t fully explain in the original post but the main issue is that the writer will work fine for months and then all of the sudden I get a bug from the client saying this table isn’t being updated any longer, when I do my testing I find that if I just replace the Oracle writer it will start working again. So it seems like it goes “stale” or something.


Hi ​@max_h 

Thanks for that suggestion, the ‘persistent connection’ has always been a bit confusing to me, I’ve had to test it a lot, and have tried it being ‘on’ and ‘off’. My oracle connection isn’t always stable so I’ve had to configure a lot with FME to try and throttle what I am sending.