Skip to main content
Solved

how to pass commit numbers to database updater transformer

  • November 28, 2017
  • 6 replies
  • 59 views

f.kemminje
Contributor
Forum|alt.badge.img+11

in my fmw file there are many number of rows updating using database transformer. after thousands of rows fme hangs and not responding. i suspect this happens because database updater not comming after some interval i think. how to pass the value for commit transaction. or did database updater committing by default after some rows?

please tell me how to pass the commit/ transaction value to database updater ?

Best answer by david_r

I'm not sure that's possible. But you could consider using a Sampler to sample "away" the first N features and then pass only the NotSampled to the DatabaseUpdater.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

6 replies

f.kemminje
Contributor
Forum|alt.badge.img+11
  • Author
  • Contributor
  • November 28, 2017

 

for your info ... i am using oracle database

david_r
Celebrity
  • Best Answer
  • November 28, 2017

I'm not sure that's possible. But you could consider using a Sampler to sample "away" the first N features and then pass only the NotSampled to the DatabaseUpdater.


f.kemminje
Contributor
Forum|alt.badge.img+11
  • Author
  • Contributor
  • November 28, 2017

@david_r But how sampler will help me. I wanted after 2000 rows updates , there should be commit.


david_r
Celebrity
  • November 28, 2017

Maybe I misunderstood your question. This is what I had in mind:


david_r
Celebrity
  • November 28, 2017

Perhaps you wanted to increase the commit interval from 1000 to 2000?

As far as I can tell, that's not possible using the DatabaseUpdater.


ravenkopelman
Safer
Forum|alt.badge.img+1

While I'm not sure about the source of the hang, I can confirm that the transaction size is not controllable within the DatabaseUpdater transformer (the Oracle writer has a default transaction size of 1000 features, for what it's worth). Please Report a Problem and reference PR#80690 to be notified of improvements to the DatabaseUpdater interface.

To gain access to advanced writer settings like transaction size, consider replacing your DatabaseUpdater with a regular Oracle writer, set to UPDATE mode.

If the hang still persists I recommend filing a bug report with as much data, workspaces, and log files that you can share.