I am using the oracle nonspatial writer in FME Desktop 2015 and I am trying to write to an Oracle table to update 2 fields. I do not see an error when the process finishes but I noticed that the changes are not reflecting in the table. I don't see any options to commit changes. How can I ensure that the changes are being committed? Do you know what would cause the changes to not be committed? Thanks for your help.
Page 1 / 1
FME will automatically do a commit after finishing the transaction.
So, that is not the cause of not seeing the changes.
Have you set the key attribute, based on which to do the update?
Can you share a screenshot of the writer feature type (table definitions in FME)?
Another good option would be using the DatabaseUpdater transformer instead of the writer.
Documentation can be found here
I set a field called ASSETNUMBER for the Update Key Column field.
I set a field called ASSETNUMBER for the Update Key Column field.
This looks good.
Do you have the attributes you want to update in the User Attributes tab?
Only those are needed.
(FME will create a SQL statement from this information).
Another good option would be using the DatabaseUpdater transformer instead of the writer.
Documentation can be found here
I used the databaseupdater transformer and it still did not update the table.
I used the databaseupdater transformer and it still did not update the table.
Can you share the log file?
Another good option would be using the DatabaseUpdater transformer instead of the writer.
Documentation can be found here
log.txt This is the log file from my process in which I read from a SDE versioned table and write to an Oracle table
log.txt This is the log file from my process in which I read from a SDE versioned table and write to an Oracle table
Looks like you use a Sampler t sample 3 objects for the Oracle table.
But all 3 objects end up in the log ffs file
D:\FME workspaces\PrimaryGasValves\TEST\geodatabase_sde2oracle_nonspatial_log.ffsI suppose you do not have the option "Redirect to FFS file" set, like this:
Opening the FFS file in the Data Inspector can help determining the issue.
Another good option would be using the DatabaseUpdater transformer instead of the writer.
Documentation can be found here
Using the DatabaseUpdater transformer worked for me! Thanks eric_jan!