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, then 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_8x.ucf and pret.sql as examples.