My Oracle Support Banner

TSFPRG Batch Ignores RESTART_CONTROL.COMMIT_MAX_CTR and Commits after each Processed Transfer (Doc ID 2583975.1)

Last updated on FEBRUARY 09, 2021

Applies to:

Oracle Retail Merchandising System - Version 16.0.1 and later
Information in this document applies to any platform.


TSFPRG batch (running 8 threads) ignores RESTART_CONTROL.COMMIT_MAX_CTR and commits after each transfer processed. Thus taking longer to complete. The problem is related to the batch doing a commit after each transfer purged. This behavior is causing high "Wait Event: log file sync" events.

Steps to reproduce:
1. Have at least 200K transfers (with shipment/shipsku) to purge.
2. Run tsfprg batch on 8 threads and increase the value of COMMIT_MAX_CTR to 1000 or 5000.
3. Notice the increased wait event on "log file sync".


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.