About Reorganizing Tables Before the Repository Merge

Upgrades: All upgrades.

Environments: Development environment only.

This topic is part of an upgrade process. See Performing a Siebel Database Upgrade.

During the repository merge process, objects from four separate repositories are read and compared. Because this is a memory-intensive process, it is recommended that you execute the REORG utility on certain tables before performing the repository merge to improve performance.

Note: Before executing the REORG utility, delete extra repositories from the database using Siebel Tools. Running the repository merge on a database with more than the four repositories which are required for the repository merge degrades repository merge performance. Before deleting extra repositories, make backups. Deletion of extra repositories can take a few hours.

The following tables receive a large number of inserts during each repository import; running REORGs on each of the following table’s ROW_ID column will significantly increase the performance of the merge:

• S_APPLET

• S_APPLET_INTL

• S_APPLET_METH_MI

• S_APPL_WEB_TMPL

• S_APPL_WTMPL_IT

• S_BOCOMP

• S_BUSCOMP_UPROP

• S_COLUMN

• S_CONTROL

• S_CONTROL_INTL

• S_CONTROL_UPROP

• S_DDOWN_OBJECT

• S_EIM_FK_MAPCOL

• S_FIELD

• S_INDEX

• S_INDEX_COLUMN

• S_INTFLD_UPROP

• S_INT_CKEY_FLD

• S_INT_COMP

• S_INT_FIELD

• S_JOIN

• S_JOIN_SPEC

• S_LIST

• S_LIST_COL_INTL

• S_LIST_COLUMN

• S_PICKMAP

• S_SCREEN_VIEW

• S_UK_ATTJOIN

• S_USER_KEY_ATT

• S_VIEW_WTMPL_IT

• S_EIM_ATT_MAP

Note: After you reorganize tables, it is recommended that you run the RUNSTATS utility to update DB2 catalog statistics.