Siebel Database Upgrade Guide > Tuning the Siebel Upgrade Files >

Rolling Back Siebel Upgrade Tuner Changes

Upgrades from: All Supported Siebel releases.

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

Platforms: Windows and UNIX only.

Databases: All databases.

This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade.

Use these procedures to discard the changes you saved from the most recent Upgrade Tuner session. You do this by rolling back the upgrade files to a previous Upgrade Tuner session.

This roll-back process is particularly useful for UNIX users. You can roll back upgrade files to a previous version on the UNIX host. You do not have to transfer the files to a Windows host and rerun Upgrade Tuner.

Upgrade File Versions

Before Upgrade Tuner saves changes to the upgrade files, it does the following:

• If this your first Upgrade Tuner session, Upgrade Tuner saves the current driver and SQL files to .orig, for example driver_upgrep_prod_77.ucf.orig.
• If this is the second session or all later sessions, Upgrade Tuner saves the current driver and SQL files to .old, for example driver_upgrep_prod_77.ucf.old.

To roll back, you replace the upgrade file with the .old or .orig version.

Guidelines for Rolling Back Upgrade Files

Use the following guidelines to roll back upgrade files:

• To roll back to the previous Upgrade Tuner session, replace the driver or SQL file with the .old version.
• To roll back to the original version of the file, before any Upgrade Tuner modifications, replace the driver or SQL file with the .orig version.
• You can roll back the driver and SQL files separately. For example, you can roll-back to the original driver file while retaining the most recent changes to SQL files.
• You do not have to roll back all SQL files at once. For example, you can roll back some SQL files while retaining the most current version of others.
• You do not have to roll back all the commands in an SQL file. You can edit the file and activate or deactivate as many commands as desired.
• Manually editing the driver_upgrep_prod_VERSION.ucf file is not recommended.
• If you roll back to a session with fewer threads, you do not have to delete any schema_t#.ddl or schema_i#.ddl thread-files. The deletion is unnecessary because Upgrade Tuner removes from the driver file the steps that execute the deleted threads.

The following procedures use driver_upgrep_prod_77.ucf and pret.sql as examples.

Rolling Back to the Previous Session

Use this procedure to discard your most-recent session and roll back to the previous session.

To roll back to the previous session

1. Save a copy of driver_upgrep_prod_77 and pret.sql to new names.
2. Copy driver_upgrep_prod_77.old to driver_upgrep_prod_77.
3. Copy pret.sql.old to pret.sql.
4. Restart Upgrade Tuner.

Rolling Back to the Original Upgrade Files

Use this procedure to discard all Upgrade Tuner changes and roll back to the original upgrade files.

To roll back to the original upgrade files

1. Save a copy of driver_upgrep_prod_77 and pret.sql.
2. Copy driver_upgrep_prod_77.orig to driver_upgrep_prod_77.
3. Copy pret.sql.org to pret.sql.

Activating or Deactivating SQL Commands Manually

Use this procedure to activate or deactivate individual zero-row SQL commands by editing the SQL file.

To activate or deactivate a command by editing an SQL file

1. Save a copy of the SQL file to a new name.
2. Open the .sql file (not the copy) and locate the desired SQL command.

   Commands begin Run_SQL_#, for example Run_SQL_100.

3. Edit the command as follows:
   • To activate the command, delete the element (Execute=N)
   • To deactivate a command, add the element (Execute=N)

     Insert the element on a line by itself after "Run_SQL_# =".

4. Save the file.

Related Topics

About Tuning Siebel Production Upgrade Files