|Bookshelf Home | Contents | Index | PDF|
This topic is part of Troubleshooting Siebel EIM Performance.
Typically, the Siebel EIM initial load is a very database-intensive process. Each row that is inserted into the base table requires modifications on the data page and the index pages of all the affected indexes. However, most of these indexes are never used during a Siebel EIM run. Index maintenance is very time-consuming for most database managers and must be avoided as much as possible.
Therefore, the goal is to determine any indexes that are unnecessary for Siebel EIM and that can be dropped for the durations of the Siebel EIM run. You can create these indexes later in batch mode by using parallel execution strategies available for the respective database platform. Using this approach can save a significant amount of time.
|Siebel Performance Tuning Guide||Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.|