Siebel Database Upgrade Guide for DB2 for z/OS > How to Perform a Siebel Database Upgrade >

Process of Tuning the Upgrade Performance

Upgrades: All upgrades.

Environments: Production test environment only. Does not apply to production environment.

This process is optional.

This process is part of a roadmap. See Roadmap for Performing a Siebel Database Upgrade.

CAUTION:  You are required to contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance with tuning your upgrade scripts. If you do not, you might invalidate your support agreement.

Use this process to run test upgrades in the production test environment so you can tune upgrade performance. Improving upgrade performance reduces downtime when you perform the production environment upgrade. The steps in this process cover standard performance tuning. For help with this process and to implement more advanced tuning, contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance.

You can also use this process to test the additive schema changes feature to verify that it does not adversely affect application functionality. The additive schema changes feature allows you to perform part of the upgrade on the production database without taking it offline. This reduces the downtime required to upgrade the production database.

Perform this process in the production test environment. Do not perform this process in the production environment.

Review the following upgrade planning and performance tuning resources before performing this process:

• 478308.1 (Article ID) on My Oracle Support. This document was formerly published as Siebel Technical Note 616. This document describes strategies for minimizing production environment downtime during an upgrade. The steps outlined in this topic are intended primarily for use with the baseline best practices described in Technical Note 616.
• Tuning the Siebel Production Upgrade Scripts. This chapter provides information on how you can improve the performance of the production environment upgrade by tuning the production upgrade scripts in a production test environment.

Set Up the Target Database

1. Back up and remove the upgraded production test database.
2. In the production test environment, install a recent backup of your production database.

   This database has not been upgraded and is called the target database. You use it to perform test upgrades as part of tuning upgrade performance.

3. Define an ODBC connection to the target database.
4. Verify that the target database is configured for optimum upgrade performance. Review the relevant topics in the following:
   • Basic Database Preparations for a Siebel Upgrade
   • The chapter in Siebel Database Upgrade Guide that describes the basic database preparations for a Siebel upgrade
5. (Optional) Run statistics on the target database if the catalog statistics require updating.
6. Perform the relevant tasks in the chapter in Siebel Database Upgrade Guide that describes how to prepare Siebel Business Applications data for upgrade.

Upgrade the Target Database Schema (upgrep + upgphys)

7. Using the upgrade files you generated during the production test upgrade, upgrade the target database by performing the following tasks:
   1. Dropping Partitioned EIM Tables.
   2. Applying Additive Upgrade Changes to the Target Database.
   3. Performing the In-Place Target Database Upgrade.
8. Upgrade the repository and import seed data. See Upgrading the Repository and Importing Seed Data. Specify the storage control file you extracted when you performed the production test upgrade (see Step 29).
9. Installing New License Keys After an Upgrade.
10. Note the time required to upgrade the database.
11. Review the upgrade logs for errors. See About the Siebel Upgrade Log Files.
12. If the upgrade contains errors that prevented completion or adversely affected performance, correct the errors and rerun the upgrade.
13. Manually Archiving Upgrade Log Files.

Tune the Upgrade Files

14. Evaluate upgrade performance, particularly the time required to complete the upgrade.
15. Do one of the following:
    • If the time required to complete the upgrade is acceptable, no further tuning is required. Perform the steps in Process of Upgrading a Siebel Production Environment.
    • If the time required to complete the upgrade is too long, perform the remaining steps in this subtopic to continue tuning upgrade performance.
    • If the time required to complete the upgrade is too long and you cannot tune further, contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance in applying advanced tuning.
16. Carefully review target database and database server configuration. Adjust as required to further improve upgrade performance.
17. Tune the upgrade files:
    • Optimizing Unload and Load Job Performance.
    • Adding the Statistics Clause to Load Cards.
18. Copy the tuned upgrade scripts to a safe location for use in the production upgrade.

Restore the Target Database

Perform these steps if you have made changes to the upgrade environment or to the upgrade files and want to run the upgrade again to verify performance improvement.

19. In the production test environment, restore the target database from backup.

    This returns the target database to its nonupgraded state so that you can perform another test upgrade.

20. In the production test environment, perform another test upgrade and evaluate upgrade performance.
21. Repeat the tuning process and perform test upgrades until upgrade performance is acceptable.
22. When you have completed tuning upgrade performance in the production test environment, delete and remove the target database.