Re-Using Scripts from Previous PeopleTools-Only Upgrade Passes

This activity regards the handling of SQL scripts that create and alter tables. In the initial and first practice pass, you generate and sometimes edit, then run the SQL scripts. You may be able to skip the generation steps and use the SQL that you previously generated and edited. However, if you have done anything to change any records, fields, or indexes, you should generate the SQL again.

If you choose to skip some of these steps, do one of the following: delete the step from your template, or change the step properties in the template so that the step will never show up in your job again. For example, to change the step properties, you can double-click the step to open the Step Properties dialog and deselect your platform.

In addition, create a new \scripts subdirectory within the PeopleTools-only upgrade Change Package and copy your desired SQL scripts from the previous pass' output directory to the PeopleTools-only upgrade Change Package's scripts directory. You will also have to modify the step that runs the script and remove any #DIRECTORY values from the parameters field. That will ensure that Change Assistant can find the scripts when it tries to run them.

The following tasks have steps that are candidates for this type of activity:

• Performing Script Modifications

• Building the Updated PeopleTools Project

• Migrating Records to New Tablespaces

• Creating PeopleTools Temporary Tables

• Creating Global Temporary Tables

• Rebuilding Oracle Indexes