Bookshelf Home | Contents | Index | Search | PDF

Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS > Migrating Data Using Siebel EIM > Setting Up EIM for DB2 >

Choosing an Optimal EIM Batch Size

---

Users can regulate EIM commit frequency in several ways, including:

Setting COMMIT EACH TABLE = TRUE.
Setting COMMIT EACH PASS = TRUE.
Adjusting batch size.

Of these, the batch size most directly influences EIM performance.

The size of EIM batches can significantly affect throughput. This occurs as a result of the number of commits that EIM must execute. While each commit is CPU-intensive, commits release page locks, thereby releasing memory and avoiding lock escalation and time-outs.

While every installation is different, you should perform initial testing with large batch sizes (except DELETE EXACT, which normally runs better with smaller batch sizes). You might want to use this as a starting point for your own processes and modify batch size based on results.

NOTE:  Processes that populate child tables might violate the maximum number of locks allowed by the system or cause contention for resources in those child tables. To avoid this, reduce the batch size of these processes.

Bookshelf Home | Contents | Index | Search | PDF