Bookshelf Home | Contents | Index | PDF |
Siebel Database Upgrade Guide > How the Siebel Database Upgrade Works > About Tuning Siebel Production Upgrade FilesUpgrades from: All Supported Siebel releases. Environments: Production test environment only. Does not apply to production environment. Platforms: Windows and UNIX only. The Upgrade Tuner allows you to tune the upgrade files generated by the Siebel Database Server Configuration Utilities. Tuning the production upgrep files can significantly reduce database downtime when performing a production environment upgrade. Upgrade Tuner displays the following information and provides the following options:
Operating System and RDBMS SupportUpgrade Tuner supports parallel threads for table and index creation for the combinations of operating system and RDBMS show in Table 16. Upgrade Tuner is not supported for IBM z/OS. Upgrade Tuner supports zero-row SQL command deactivation for the combinations of operating system and RDBMS shown in Table 17. For information on which versions and releases of the operating systems and RDBMS products that Oracle supports for Siebel products, see Siebel System Requirements and Supported Platforms on Oracle Technology Network. Upgrade Tuner is part of the Siebel Server and runs only under Microsoft Windows. Upgrade Tuner does not run under UNIX. To tune UNIX production upgrade files, you must copy them to a Windows platform, tune them, and move them back to the UNIX platform. Scripts are provided to move the files. If you are a UNIX user and do not have a Siebel Server for Windows, contact your account manager or Oracle Global Customer Support to obtain one. When to Use Upgrade TunerUse Upgrade Tuner in the production test environment to tune the upgrade files that perform the production upgrep. There is no need to tune the upgrade files that perform the production upgphys. You also do not need to tune the upgrade files that perform the development environment upgrep or upgphys. Upgrade Tuner ModesWhen you start Upgrade Tuner it displays four tabs: Process Information TabThis page displays the information sources that Upgrade Tuner is using. These sources include the Logparse summary.xml file, master .ucf file, and driver .ucf file. You cannot edit the information on this page. Upgrade Tuner obtains the information by reading the Parallelize Table Creation and Parallelize Index Creation TabsThe Parallelize Table Creation page and the Parallelize Index Creation page both have the same layout. These pages allow you to do the following:
Creating parallel threads improves the upgrade performance by reducing the total time to create tables and indexes. You can create up to nine parallel threads. Each thread can have a maximum of ten tables or indexes. Tables or indexes not assigned to a parallel thread remain in the serial thread. Deactivate 0-Row SQLsThis page allows you to activate or deactivate the SQL statements that do not affect any table rows and therefore any data. This capability improves the upgrade performance by eliminating SQL statements that may not apply to your data. This page lists only the SQL files that are executed natively by the RDBMS. It does not list SQL files that are executed using odbcsql. Files Required to Run Upgrade TunerUpgrade Tuner requires the following files. The location of the files is the same on both Windows and UNIX hosts. Table 18 displays these files. How Upgrade Tuner Modifies FilesWhen you save your changes, Upgrade Tuner modifies the upgrade files. These are the files the Upgrade Wizard uses to upgrade the database. These files are as follows: Driver Configuration FileWhen you add or remove parallel threads and save your changes, Upgrade Tuner modifies the driver configuration file, for example The following actions are examples of steps that can appear in the driver configuration file:
Upgrade Tuner manages the driver configuration file as follows:
This file management strategy preserves the previous set of revisions to the file. It also preserves the original version of the file. Schema.ddl FileWhen you run the Upgrade Wizard after the production upgrep it reads the driver file. The driver file contains steps that call the ddlimp utility. This utility uses schema.ddl as input to upgrade your database schema. In the Parallelize Table Creation and Parallelize Index Creation pages, Upgrade Tuner displays the creation times for the tables and indexes in the schema.ddl file. When you create parallel threads, Upgrade Tuner creates thread-files that have the same format as schema.ddl but contain only the table or index creation steps in the thread. Upgrade Tuner then adds steps to the driver file. These steps call the ddlimp utility, and specify the thread-files as input. Upgrade Tuner manages schema.ddl and thread-files as follows:
In the driver file, the order of execution of steps for schema.ddl and the thread-files is as follows:
For both table and index creation, the parallel threads are executed first followed by the serial thread (schema.ddl). TIP: To locate thread-file steps in the driver_upgrep_prod ucf file, query for "schema_". SQL FilesWhen you make changes in the Deactivate 0-Row SQLs page, Upgrade Tuner makes changes to the SQL file containing the SQL command. Because the SQL file is already a step in the driver file, Upgrade Tuner does not modify the driver file. Upgrade Tuner manages the SQL files as follows:
This file management strategy preserves the previous set of revisions to the file. It also preserves the original version of the file. |
Siebel Database Upgrade Guide | Copyright © 2008, Oracle. All rights reserved. | |