Bookshelf Home | Contents | Index | PDF |
Siebel Database Upgrade Guide for DB2 for z/OS > Performing the Siebel Repository Merge > About Reorganizing Tables Before the Repository MergeEnvironments: Development environment only. This topic is part of an upgrade process. See How to Perform 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:
NOTE: After you reorganize tables, it is recommended that you run the RUNSTATS utility to update DB2 catalog statistics. |
Siebel Database Upgrade Guide for DB2 for z/OS | Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |