Implementing Siebel eBusiness Applications on DB2 UDB for z/OS and OS/390 > Migrating Data Using Siebel EIM >
Considerations for EIM Tables
Consider the following issues when working with EIM tables.
Updating the S_LST_OF_VAL Table
The BU_ID column in the S_LST_OF_VAL base table can have only one or very few distinct values. When this happens, the DB2 optimizer often needlessly performs a table scan through all rows in the S_LST_OF_VAL table.
To avoid this problem and speed up the query, modify the statistics data by running the following SQL statements:
update sysibm.sysindexes set firstkeycardf=1000 where
update sysibm.syscolumns set colcardf = 1000 where
tbname='S_LST_OF_VAL' and name='BU_ID';
NOTE: Depending on the data you are working with, you might need to run other SQL statements ahead of time.
Resolving Performance Degradation During the Load Process
When executing the EIM load process, performance might degrade noticeably over time, after subsequent batch loads. This performance degradation is often due to outdated statistics on the tables being loaded. To resolve the problem, update statistics on the target base tables.
Resolving Errors in the EIM Process
Perform the steps below to resolve errors that might occur during your EIM process:
- If EIM aborts with the following generic error, then the user account running EIM does not have EXECUTE privileges on the DSNUTILS stored procedure:
DSNUGMAP - USER
NOT AUTHORIZED FOR RUNSTATS UTILITY ON
See Using the RUNSTATS Utility for information about required permissions. Alternatively, you can run EIM with the following setting:
UPDATE STATISTICS = FALSE
- If your EIM process fails with the following error message, then the DSNZPARM parameter RETVLCFK might be set incorrectly.
EIM-00205 Failed To Load the Application Dictionary
Siebel eBusiness Applications require the setting
RETVLCFK=NO. For information on DSNZPARM settings see Preparing for Implementation on the DB2 Host.
- If EIM terminates during a DELETE EXACT process involving deletion of child records, the following error indicates that the maximum allowable locks were exceeded:
EIM Fails - Max Locks Exceeded on DELETE EXACT
This causes the child records to be orphaned, because the delete to the parent table has already been committed.
You can avoid this error by specifying the following in your
COMMIT EACH PASS = FALSE
COMMIT EACH TABLE = FALSE
ROLLBACK ON ERROR = TRUE