Upgrade Guide > How to Perform a Siebel Database Upgrade >
Process of Tuning Siebel Upgrade Performance
Upgrades: All Siebel upgrades.
Environments: Production test, production.
This process is optional.
This process is part of a road map. See Road Map 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 Oracle's Siebel Expert Services.
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:
- 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 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 Upgrade Tuner. To obtain a Windows version of Siebel Server, contact your account manager or Oracle.
Set Up the Target Database
- 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.
- 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.
- Define an ODBC connection to the target database.
- Verify that the target database and RDBMS server are configured for optimum upgrade performance:
- Preparing Siebel Tables and Views for Upgrade.
- Run statistics on the target database. This optimizes query performance.
- UNIX users.Securing AIX Memory Allocation Segment Space for the Siebel Database.
- Perform the tasks in Preparing Siebel Application Data for Upgrade.
Upgrade the Target Database Schema (upgrep)
- In the production test environment, run the Database Server Configuration Utilities:
- In the production test environment, run Siebel Upgrade Wizard. See Starting the Siebel Upgrade Wizard.
Note the time required to upgrade the database.
- Review the upgrade logs for errors:
- If the upgrade contains errors that prevented completion or adversely affected performance, correct the errors and rerun the upgrade
Tune the Upgrade Files
- Evaluate upgrade performance, particularly the time required to complete the upgrade.
- 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 Oracle's Siebel Expert Services to apply advanced tuning.
- Carefully review target database and RDBMS server configuration. Adjust as needed to further improve upgrade performance.
- Run Upgrade Tuner to tune the upgrade files:
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.
- 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.
- In the production test environment, perform another test upgrade and evaluate upgrade performance.
- 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.
- In the production test environment, delete and remove the target database.
- In the production test environment, restore the production-test final database from backup.