Adding Internet Explorer Support for Siebel 8

The following configuration changes need to be made on the Siebel Application Server for each Siebel installation, so that it knows the capabilities of the IE8 browser. This configuration step is mandatory for all Siebel versions whenever IE8 is used in any environment, regardless of patch level:

Handling EIM Failures after Siebel Upgrade

After upgrading Siebel applications to a higher release, certain columns that were previously not List-of-Value (LOV) bounded became LOV bounded that could cause EIM import failure Oracle Siebel highly recommends that users evaluate the potential impact of schema upgrade before they perform any EIM loading in a new release.

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.

What is the recommended number of rows that can be loaded in a single batch?

For an initial load, you can use 30,000 rows for a large batch. For ongoing loads, you can use 20,000 rows for a large batch. You should not exceed 100,000 rows in a large batch.
Furthermore, you should limit the number of records in the interface tables to those that are being processed. For example, if you have determined that the optimal batch size for your system is 19,000 rows per patch and you are going to be running

How can I tune my EIM batches to improve performance?

You should try the following options to improve EIM performance:

Verify that all indices exist for the tables involved.

Limit tables and columns to be processed using ONLY BASE TABLES/COLUMNS configuration parameters to minimize EIM processing.

Consider switching off transaction logging during the EIM run. This will definitely improve performance. However, it must be balanced with the need for mobile users to reextract afterward.

How do I use the DELETE EXACT parameter to delete data from base tables other than the target base table?

To use the DELETE EXACT parameter to delete data from base tables other than the target base table, specify the user key columns only for a single base table for each row in the interface table. When specifying rows for exact deletion, make sure any columns not necessary to specify the row to be deleted are NULL to avoid problems with deleting from the wrong base table. EIM tries to enforce this behavior by requiring other user key columns to be NULL.

Recent content