DB2 10.5 for Linux, UNIX, and Windows

commit_period - Commit period configuration parameter

Specifies the number of seconds between committed transactions.

Configuration type: Ingest utility
Applies to: Ingest utility
Parameter type: Configurable
Default [range]: 1 [0 to 2,678,400 (31 days)]
Unit of measure: Seconds

At each flush, the ingest utility checks the number of seconds since the last commit. If it is greater than or equal to the setting of commit_period, the ingest utility issues a commit.

If commit_period is set to 0, the commit_count configuration parameter is used, meaning that transactions are to be committed based upon the number of rows.

When neither commit_count nor commit_period is specified, the commit_period default setting of 1 second is used.

If both commit_count and commit_period are specified, the ingest utility honors both; that is, it issues a commit when it has written the specified number of rows or if there has not been a commit within the specified number of seconds.

Recommendations: If the row size is small, set commit_period to a large value. If the row size is large, set commit_period to a small value.

If commit_period is set to too large a value, it is likely the lock list or the transaction log will fill up. In that case, the INGEST command terminates with error SQL0912N or SQL0964C. If you get SQL0912N or SQL0964C and you have the retry_count configuration parameter set, the ingest utility does both of the following actions

adjusts the setting of either commit_count or commit_period, or both and issues a warning message
issues a commit and retries the operation