|Bookshelf Home | Contents | Index | PDF|
The initial load of data is typically a database-intensive process. Each row that is inserted into the base table requires modifications, not only to the table itself, but to all its affected indexes. However, most of these indexes are never used during an initial load process.
You can usually improve performance by determining which base table indexes are unused by EIM during the import process and dropping them prior to the initial load. You must later re-create these indexes.
Dropping unused triggers can improve import performance by reducing the system overhead used to verify trigger constraints. You can use the Generate Triggers (GenTrig) component from Siebel Server Tasks to drop the triggers and to re-create them later on. This component must be in the Enabled state. For details on how to work with Generate Triggers, see Siebel Business Process Framework: Workflow Guide.
To improve the EIM import and update SQL performance, set PCTFREE for table spaces and indexes to a value of 20 or 30 prior to the EIM initial load, and maintain these settings at 20 or 30 for subsequent loads.
Alter base table spaces to PCTFREE and FREEPAGE values of 20 or 30 for subsequent import processes. It is also recommended that you load or reorganize any altered items before the new values take effect. The following example demonstrates how to set these values for your table spaces and indexes. Substitute your own table space and index names for your implementation.
ALTER INDEX SIDB0401.S_ADDR_ORG_M6 PCTFREE 20;
Siebel transaction logging is unnecessary during an initial EIM load, and should be disabled by setting
|Implementing Siebel Business Applications on DB2 UDB for z/OS||Copyright © 2008, Oracle. All rights reserved.|