Bookshelf Home | Contents | Index | Search | PDF

Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS > Maintenance Considerations for zSeries >

Reorganizing Table Spaces, Partitions, and Indexes

---

It is recommended that you reorganize tables spaces, partitions, and indexes that have a tendency to become disorganized or fragmented.

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, partitions, and indexes, because disorganization and fragmentation of these objects can affect performance significantly. (For a list of Siebel tables to monitor for reorganization, see Table 7.)

You should not reorganize S_ESCL_LOG, S_DOCK_INIT_ITEM, and all S_DOCK_INITM_%% tables (where % is a digit).

You should not use 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) then loadstat.sql. For more information on how to run these utilities, see Updating Statistics.

CAUTION:  You should not use online REORG of Siebel repository table spaces. To avoid adversely affecting the Siebel application, perform reorganization of Siebel repository tables paces during scheduled application downtime.

Bookshelf Home | Contents | Index | Search | PDF