A change plan is the set of changes that you
want to make to your DB2 for Linux, UNIX or Windows database. A change
plan also includes the specification resources, change commands, and
metadata about how the changes will be implemented.
Creating a change plan
Use a change plan to manage changes to your database objects
and run those changes against your target database.
Modifying existing changes in a change plan
You can make additional changes to objects that already
have planned changes. For example, you might want to change the attributes
of a table that is being created or one that is being altered.
Deploying a change plan to the database
Generate the commands to implement the changes for a change
plan. The commands are generated from the change plan. Then, run the
generated commands to apply the changes to the database.
Rolling back changes from a deployed change plan
After the changes in a change plan are run and applied
to the database catalog, you might decide that the changes need to
be backed out. Running an undo script rolls back the changes.