|Bookshelf Home | Contents | Index | PDF|
No strict guidelines can be offered as to which table spaces, partitions, and indexes might require reorganization due to the variety in application and customer operation variables at any given customer site. However, database administrators should pay attention to the status of large or heavily used table spaces and indexes, because fragmentation of these objects can affect performance significantly. (For a list of suggested Siebel tables to monitor for reorganization, see Table 8.)
You should avoid using online REORG of Siebel repository table spaces. Reorganization of Siebel repository table spaces should be scheduled during application downtime to avoid adversely affecting the Siebel application.
After you reorganize table spaces and indexes, it is recommended that you execute rstat390 (from midtier) or RUNSTATS (on the DB2 host) . For more information on how to run these utilities, see About the RUNSTATS Utility.
|Implementing Siebel eBusiness Applications on DB2 UDB for z/OS and OS/390|