Siebel Database Upgrade Guide > How to Perform a Siebel Database Upgrade >

Process of Tuning Siebel Upgrade Performance

Upgrades from: All Supported Siebel releases.

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

Platforms: Windows and UNIX only. This topic does not apply to IBM z/OS.

NOTE:  This process is optional.

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

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. To implement more advanced tuning, including high-availability tuning, contact your Oracle sales representative for Oracle Advanced Customer Services.

Also use this process to test the additive schema changes feature. This 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. Test the additive schema changes feature to verify that it does not adversely affect the operation of the application.

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:

• About Siebel Additive Schema Changes Mode
• Bulletin 478308.1 (Doc ID) on OracleMetalink 3. This document was previously published as Siebel Technical Note 616. This Bulletin describes the strategies for minimizing production environment downtime during an upgrade. The steps that follow are intended primarily for use with the Baseline best practices described in Bulletin 478308.1 (Doc ID).
• Tuning the Siebel Upgrade Files. This chapter provides detailed information on how to use Upgrade Tuner.

UNIX users. You must have a Siebel Server installed on a Windows host to run the Upgrade Tuner. To obtain a Windows version of Siebel Server, contact your account manager or Oracle Global Customer Support.

CAUTION:  Do not use this topic to tune upgrade performance on IBM z/OS. Instead, refer to Siebel Database Upgrade Guide for DB2 UDB for z/OS.

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 will 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 and RDBMS server are configured for optimum upgrade performance:
   • Preparing an IBM DB2 Database for a Siebel Upgrade.
   • Preparing an Oracle Database for a Siebel Upgrade.
   • Preparing a Microsoft SQL Server Database for a Siebel Upgrade.
5. Preparing Siebel Tables and Views for Upgrade.
6. Run statistics on the target database. This optimizes query performance.
7. UNIX users. Securing AIX Memory Allocation Segment Space for the Siebel Database.
8. Perform the tasks in Preparing Siebel Application Data for Upgrade.

Testing Additive Schema Changes

If you do not plan to run additive schema changes on the production database in the production environment, you do not need to perform the steps in this topic.

Perform these steps on the target database.

9. Review About Siebel Additive Schema Changes Mode.
10. (Optional) Changing the Siebel Database Configuration Utilities Language.
11. In the production test environment, run the Database Configuration Wizard:
    • Preparing to Run the Siebel Database Configuration Wizard.
    • Running the Siebel Database Configuration Wizard Under Windows.
    • Running the Siebel Database Configuration Wizard Under UNIX.
12. Choose Apply Additive Schema Changes mode.

    The Apply Additive Schema Changes mode identifies changes that can be made to the target database without taking it offline.

    Windows. You will not be prompted whether you want to run the Upgrade Wizard. Instead, the Upgrade Wizard starts automatically, and creates the schema.additive.sql script. The Upgrade Wizard does not run the script against the target database.

13. UNIX. Run the Siebel Upgrade Wizard.

    See Starting the Siebel Upgrade Wizard

    Specify master_additive_gen.ucf as the input file.

    The Upgrade Wizard generates the schema.additive.sql script. It does not run the script against the target database.

14. Run the SQL script against the target database.

    See Applying Siebel Additive Schema Changes.

15. Thoroughly review the operation of all applications. Verify that applying the additive schema changes has not adversely affected the operation of all applications.
16. If applying additive schema changes adversely affects the operation of the applications, do the following:
    1. For help diagnosing the cause of the problem and help in taking corrective action create a service request (SR) on OracleMetalink 3. Alternatively, you can phone Global Customer Support directly to create a service request or get a status update on your current SR. Support phone numbers remain the same and are listed on OracleMetalink 3.
    2. Restore the target database from backup before proceeding with further upgrade tuning.
    3. Do not use the additive schema changes feature during your production upgrade.
17. If applications function normally, continue with upgrade tuning. Consider using the additive schema changes feature during your production upgrade.

Upgrading the Target Database (upgrep and upgphys)

18. (Optional) Changing the Siebel Database Configuration Utilities Language.
19. In the production test environment, run the Database Configuration Wizard:
    • Preparing to Run the Siebel Database Configuration Wizard.
    • Running the Siebel Database Configuration Wizard Under Windows.
    • Running the Siebel Database Configuration Wizard Under UNIX.

      Choose the following settings:

    • Upgrade Options: Upgrade Siebel Database Schema (upgrep + upgphys)
    • Environment Type: Production
20. In the production test environment, run Siebel Upgrade Wizard.

    See Starting the Siebel Upgrade Wizard.

    Note the time required to upgrade the database.

21. Review the upgrade log files for errors:
    • Summarizing Siebel Log Files Using the Logparse Utility.
    • Reviewing Siebel Upgrade Log Files for Errors.
22. If the upgrade contains errors that prevented completion or adversely affected performance, correct the errors and rerun the upgrade.
23. Manually Archiving Siebel Upgrade Log Files.

Tuning the Upgrade Files

24. Evaluate upgrade performance, particularly the time required to complete the upgrade.
25. 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 topic to continue tuning upgrade performance.
    • If the time required to complete the upgrade is too long and you cannot tune further, contact Expert Services to apply advanced tuning.
26. Carefully review target database and RDBMS server configuration. Adjust as needed to further improve upgrade performance.
27. Run Upgrade Tuner to tune the upgrade files:
    • UNIX users. Transferring UNIX Files for Use by Siebel Upgrade Tuner.
    • Starting and Stopping Siebel Upgrade Tuner.
    • Managing Parallel Threads Using Siebel Upgrade Tuner.
    • Managing Zero-Row SQL Commands Using Siebel Upgrade Tuner.

      To roll back changes you have made in previous Upgrade Tuner sessions, see Rolling Back Siebel Upgrade Tuner Changes.

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.

28. 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.

29. In the production test environment, apply additive schema changes again as desired.
30. Perform another test upgrade and evaluate upgrade performance.
31. 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.

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