Siebel Installation Guide for UNIX > Configuring the RDBMS > Configuring an IBM DB2 Database for Siebel Business Applications >

Guidelines for Managing IBM DB2 Fragmentation

No strict guidelines can be offered as to which tables and indexes might be fragmented, because of the variety in application and customer operation variables at any given customer site. However, DBAs must pay attention to the status of large or heavily used tables, because fragmentation of these tables can affect performance significantly. For a list of these Siebel tables, see Siebel Deployment Planning Guide.

NOTE:  Do not reorganize S_ESCL_LOG, S_DOCK_INIT_ITEM, S_ESCL_ACTN_REQ, S_APSRVR_REQ, and all tables named S_DOCK_INITM_%% (in this table name, % is a digit), because these tables are defined to be in append mode.

This topic is part of Configuring an IBM DB2 Database for Siebel Business Applications.

Use the following strategy to manage table fragmentation:

• Run REORGCHK on heavily used tables, and then review the resulting reports and extract a list of any fragmented objects.
• Based on the results of REORGCHK, reorganize any tables, as needed, by running REORG TABLE. For details on how to reorganize tables or indexes, see the following:
  • 477378.1 (Article ID) on My Oracle Support. This document was previously published as Siebel FAQ 2072.
  • 477402.1 (Article ID) on My Oracle Support. This document was previously published as Siebel FAQ 2073.
• After reorganizing tables, update statistics by using the runstats utility on any reorganized tables with the following minimum parameters:

  runstats on table tablename with distribution and detailed indexes all shrlevel change

  You might add other parameters as required, but use the shrlevel change parameter to allow concurrent access to your tables while runstats executes.

  CAUTION:  The runstats utility overwrites statistics loaded by Siebel Business Applications. If you use runstats, then always execute loadstats.sql afterwards, by using either DB2 CLP or odbcsql. Otherwise, valuable statistics will be lost.

  To run loadstats.sql by using odbcsql, use the following command:

  odbcsql /s DATASOURCE_NAME /u username /p password /v separator siebel_root/dbsrvr/db2udb/loadstats.sql TABLEOWNER_NAME