Siebel Database Upgrade Guide for DB2 UDB for z/OS > Planning A Siebel Database Upgrade >
About Creating a Schedule for the Upgrade
Develop a plan for your upgrade based on the objectives and constraints for your deployment.
If you are migrating multiple languages from a prior version, plan extra time for the repository merge process. The expected merge time may increase with the number of languages in the repository. You also might need to plan for additional installation-related tasks.
The following procedures may reduce the time required for your upgrade:
- Run selected processes in advance of the upgrade.
Certain preupgrade tasks can be run at any time prior to the upgrade. These procedures can be performed in advance either for testing purposes or to accommodate down-time constraints.
Examples of procedures that can be performed by a database administrator in advance of your upgrade include Preparing the Storage Layout of the Schema.
- Apply additive schema changes to the production database ahead of the target database in-place upgrade. See About Siebel Additive Schema Upgrade Changes.
- Prepare select processes to run in parallel.
If a large table such as
S_EVT_ACT is partitioned, it can run in parallel by transferring shipped statements into the numbered SQL statement.
Do not start a new development effort until after the new version has been rolled out. This is especially important when you are upgrading from Release 6.2.1 to Release 8.0. There are significant user interface differences between the two versions, and you must change existing functionality before moving on to customized functionality.