for your info ... i am using oracle database
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.
@david_r But how sampler will help me. I wanted after 2000 rows updates , there should be commit.
Maybe I misunderstood your question. This is what I had in mind:
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.
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.