Upgrade Guide for DB2 UDB for z/OS > How to Perform the Upgrade >

Process of Tuning Upgrade Performance

Upgrades: All upgrades.

Environments: Production test environment only.

This process is optional.

This process is part of a road map. See Road Map for Performing the Upgrade.

CAUTION:  You must contact Siebel Expert Services before tuning upgrade scripts. If you do not, you may 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 Siebel Expert Services.

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

• Technical Note 616. This Technical Note describes strategies for minimizing production environment downtime during an upgrade. The steps in this process are intended primarily for use with the Baseline best practices described in Technical Note 616.
• Tuning the 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.

   This preserves seed data and metadata changes you have made that must be migrated to the production environment. This database is called the production-test final 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. See Basic Database Preparations.
5. Run statistics on the target database. This optimizes query performance.
6. Perform the tasks in Preparing Application Data for Upgrade.

Upgrade the Target Database Schema (upgrep + upgphys)

7. In the production test environment, run the Database Server Configuration Utility:
   • Preparing to Run the Database Server Configuration Utility.
   • Running the Database Server Configuration Utility Under Windows.
   • Running the Database Server Configuration Utility Under UNIX.

     Choose the following settings:

   • Upgrade Options: Upgrade Siebel Database Schema (upgrep + upgphys)
   • Environment Type: Production test.

     Enter Yes to launch the Siebel Upgrade Wizard. SQL commands are executed on the production test environment database until the Upgrade Wizard stops at the First Pause.

8. Review the following topic and perform the procedure if applicable: Migrating Address Data from Custom Extension Columns.
9. Preparing the zSeries Host Environment.
10. Resuming the Siebel Upgrade Wizard After the First Pause.
11. Transferring Control Cards and Schema DDL Files to the zSeries Host.
12. Preparing the Schema and JCL Files on the zSeries Host.
13. Installing Stored Procedures on the zSeries Host.
14. Preparing Siebel-Scheduled Jobs on the zSeries Host.
15. Optimizing the Target Job Stream, Part 1.
16. Optimizing Old-Schema Index Rebuild Jobstreams.
17. Loading Log Tables on the Source Database.
18. Loading Log Tables on the Target Database.
19. Executing the Upgrade on the zSeries Host (Phase 1 of 2).
20. Resuming the Siebel Upgrade Wizard on the Midtier After the Second Pause.
21. Transferring the Index Schema to the zSeries Host.
22. Preparing Siebel-Scheduled JCL.
23. Optimizing the Target Job Stream, Part 2.
24. Executing the Upgrade on the zSeries Host (Phase 2 of 2).
25. Performing Intersection Table Maintenance.
26. Resuming the Siebel Upgrade Wizard on the Midtier After the Third Pause.

    Note the time required to upgrade the database.

27. Review the upgrade logs for errors. See Reviewing Upgrade Log Files for Errors.
28. If the upgrade contains errors that prevented completion or adversely affected performance, correct the errors and rerun the upgrade.

Tune the Upgrade Files

29. Evaluate upgrade performance, particularly the time required to complete the upgrade.
30. Do one of the following:
    • If the time required to complete the upgrade is acceptable, no further tuning is needed. Perform the steps in Restore the Production-Test Final Database.
    • If the time required to complete the upgrade is too long, perform the remaining steps in this section to continue tuning upgrade performance.
    • If the time required to complete the upgrade is too long and you cannot tune further, contact Siebel Expert Services to apply advanced tuning.
31. Carefully review target database and RDBMS server configuration. Adjust as needed to further improve upgrade performance.
32. Tune the upgrade files:
    • Optimizing Unload and Load Job Performance.
    • Adding the Statistics Clause to Load Cards.
    • About Deactivating Jobs That Do Not Process Data.
33. 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.

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

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

35. In the production test environment, perform another test upgrade and evaluate upgrade performance.
36. Repeat the tuning process and perform test-upgrades until upgrade performance is acceptable.

Restore the Production-Test Final Database

Perform these steps only if you have completed tuning upgrade performance.

37. In the production test environment, delete and remove the target database.
38. In the production test environment, restore the production-test final database from backup.