|
Siebel Database Upgrade Guide > Overview of Performing a Siebel Database Upgrade >
Process of Tuning Siebel Upgrade Performance
Platforms: Windows and UNIX only. NOTE: This process is optional.
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. NOTE: Links to other topics in this guide are provided throughout this chapter. These links are meant to provide additional information that cannot be provided in these brief overviews. You must, however, perform the upgrade in the proper order. For information on general planning, see this chapter as well as Siebel Database Upgrade Planning, and Application Planning for a Siebel Upgrade. To begin the process of upgrading your Siebel database, see Preparing for Siebel Database Upgrade, then refer to each subsequent chapter.
Review the following upgrade planning and performance tuning resources before performing this process:
- About Siebel Additive Schema Changes Mode
- 478308.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Technical Note 616. This article describes the strategies for minimizing production environment downtime during an upgrade. The steps that follow are intended primarily for use with the baseline guidelines described in 478308.1 (Article 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 for z/OS.
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.
Test Additive Schema Changes
If you do not plan to run additive schema changes on the production database in the production environment, then you do not need to perform the steps in this topic. Perform these steps on the target database.
- Review About Siebel Additive Schema Changes Mode.
- (Optional) Changing the Siebel Database Configuration Utilities Language.
- In the production test environment, run the Database Configuration Wizard:
- 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.
- 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.
- Run the SQL script against the target database.
See Applying Siebel Additive Schema Changes.
- Thoroughly review the operation of all applications. Verify that applying the additive schema changes has not adversely affected the operation of all applications.
- If applying additive schema changes adversely affects the operation of the applications, then do the following:
- For help diagnosing the cause of the problem and help in taking corrective action create a service request (SR) on My Oracle Support. 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 My Oracle Support.
- Restore the target database from backup before proceeding with further upgrade tuning.
- Do not use the additive schema changes feature during your production upgrade.
- If applications function normally, then continue with upgrade tuning. Consider using the additive schema changes feature during your production upgrade.
Upgrade the Target Database (upgrep and upgphys)
- (Optional) Changing the Siebel Database Configuration Utilities Language.
- In the production test environment, run the Database Configuration Wizard:
- 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 log files for errors:
- If the upgrade contains errors that prevented completion or adversely affected performance, then correct the errors and rerun the upgrade.
- Manually Archiving Siebel Upgrade Log Files.
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, then 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, then 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, then contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle's Application 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, apply additive schema changes again as desired.
- 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.
|
