Bookshelf v7.5: Planning the Distribution of Your Database Objects

Regardless of the RDBMS you implement and your chosen disk arrangement, be sure that you properly distribute the following types of database objects:

In most implementations, the Siebel tables listed in Table 19 and their corresponding indexes are either the most commonly used, or they can be large in some or in all deployments. For example, the tables S_EVT_ACT, S_CONTACT, and S_ORG_EXT are large in all enterprise-level deployments of Siebel eBusiness Applications. These tables and indexes should be separated across devices. As a general rule, indexes should be in a different tablespace and, if possible, on different physical devices from the tables on which they are created.

Table 19. Most Frequently Used and Largest Siebel Tables
Table Names
`S_ACCNT_CHRCTR`	`S_INVOICE`
`S_ACCNT_CO_MSTR`	`S_INVOICE_ITEM`
`S_ACCNT_POSTN`	`S_INV_LGR_ENTRY`
`S_ADDR_ORG`	`S_OPTY_POSTN`
`S_ADDR_PER`	`S_OPTY_PROD`
`S_ASSET`	`S_OPTY_TERR`
`S_CALL_LST_CON`	`S_OPTY_POSTN`
`S_CON_CHRCTR`	`S_ORG_EXT`
`S_CON_TERR`	`S_ORG_TERR`
`S_ACCNT_CHRCTR`	`S_PARTY`
`S_CRSE_TSTRUN`	`S_PARTY_PER`
`S_CRSE_TSTRUN_A`	`S_PARTY_REL`
`S_CS_RUN`	`S_PARTY_RPT_REL`
`S_CS_RUN_ANSWR`	`S_POSTN_CON`
`S_CTLGCAT_PATH`	`S_PROC_REQ`
`S_CYC_CNT_ASSET`	`S_PROD_BASELINE`
`S_DNB_CON_MRC`	`S_PROD_CONSUME`
`S_DNB_ORG`	`S_PROD_SHIPMENT`
`S_DNB_ORG_SIC`	`S_PROD_TARGET`
`S_DNB_UPDATE`	`S_QUOTE_ITEM`
`S_DOCK_INIT_ITEM`	`S_SRM_REPLY`
`S_DOCK_TXN_LOG`	`S_SRM_REQUEST`
`S_DOCK_TXN_LOGT`	`S_SRM_REQ_PARAM`
`S_DOCK_TXN_SET`	`S_SRV_REQ`
`S_DOCK_TXN_SETT`
`S_ESCL_ACTN_REQ`
`S_ESCL_LOG`
`S_ESCL_REQ`
`S_EVT_ACT`
`S_EXP_ITEM`
`S_EXP_RPT`
`S_EXP_RPT_APPR`
`S_IC_CALC`
`S_IC_CALC_IT`
`S_IC_CMPNT_EARN`
`S_IC_TXN`
`S_IC_TXN_IT`
`S_IC_TXN_POSTN`
`S_INVC_ITM_DTL`
`S_INVLOC_ROLLUP`

If you use Siebel Enterprise Integration Manager (EIM) frequently, you may want to put the interface tables (names starting with EIM_) on different devices from the Siebel base tables, because both are accessed simultaneously during EIM operations.

NOTE: Siebel tablespaces on DB2 UDB should be database-managed tablespaces (DMS) rather than system-managed tablespaces (SMS).

Reorganizing Fragmented Tables and Indexes

It is recommended that you use the REORGCHK utility to reorganize tables and indexes that have a tendency to become fragmented.

No strict guidelines can be offered as to which tables and indexes may be fragmented due to the variety in application and customer operation variables at any given customer site. However, database administrators (DBAs) should pay attention to the status of large or heavily used tables, since fragmentation of these tables can affect performance significantly. (For a list of these Siebel tables, see Table 19.)

It is not a good idea to reorganize S_ESCL_LOG, S_DOCK_INIT_ITEM, S_ESCL_ACTN_REQ, S_EVT_ACT, S_OPTY_POSTN, s_OPTY_TERR, S_ORG_EXT, S_APSRVR_REQ, and all S_DOCK_INITM_%% tables (where % is a digit), because these tables are defined to be in append mode.