Siebel EIM Batch Size could have an adverse impact on Siebel Remote and Replication Manager Environments

In the "Advanced Usage" chapter of the Siebel "Enterprise Integration Manager and Administration Guide", it is recommended that batch sizes of 5,000 records or less be used. Running Enterprise Integration Manager Tasks with batch sizes greater than 5,000 records could result in a stalled Transaction Router or memory leak in Replication Agent server component when merging records into regional node database. If the Transaction Router is stalled, remote users will not receive updates from the Server Database. In order to resolve the behavior, all remote users must be re-extracted. When using replication manager with a batch size over 5000 records, , the router needs to run more SQL to determine visibility and in doing this large amounts of memory will be used and this may lead to memory related failure of the Replication Agent server component.

Workaround or Resolution

It is recommended that when running Enterprise Integration Manager, batch sizes should be no larger than 5,000. Note also that smaller batch sizes (no larger than 2,000) are recommended to improve performance, as stated in FAQ 1097: How can I tune my EIM batches to improve performance?
Note that for importing or updating data, the batch size can explicitly be set. For deleting records using Delete Exact=TRUE, the batch size can be explicitly set.

However, if deleting records using Delete Matches, do not explicitly set a batch size in the Interface Table. In order to ensure that the delete affects 2,000 or fewer records, simply run a select statement including the Delete Matches criteria directly against the base table to determine the total number of records that will be deleted.