Scenario: Promoting changes from one system to another

This scenario supposes that you are asked to promote the changes that were made to the human resources database on the development system to the test system.

About this task

This task requires you to determine the differences between the development and test system and apply the changes to the test system.

Assume that versions for the current state of the databases exist (Release 11C in DEV and Release 11B in TEST). You will compare the two versions to generate a delta changes data set that contains the SQL statements that represent the differences, transfer the delta changes data set to the test system, import the delta changes data set on the test system as a new change, and then apply the changes to the test database.

In synchronizing the human resources database, you have the following goals:
  • Ensure that there is a snapshot of the database structures for fallback purposes.
  • Capture the changes that are made on the test system for auditing purposes.

The following steps show you how you might use Change Management to make these changes and achieve your goals:

Procedure

  1. On the source system (the development system), use the current versions of the development and test databases to identify the differences between the databases and promote the differences to the target system (the test system). To find and promote the differences in a delta changes data set:
    1. Go to the Change Management main menu and display the Manage Changes panel.
    2. Select the option to create a delta changes file for the target system.
    3. Identify the version of the test database as the starting version and the version of the development database as the ending version. Provide a name for the job that will generate the delta changes data set and a name for the delta changes data set.
      The starting version is a snapshot of the objects before changes are made, and the ending version is a snapshot of the objects after changes are made. In this scenario, you want to bring the level of the test system up to the level of the development system.
    4. Register the change in the Change Management database.
      You will be prompted to register the changes that are being promoted.
    5. Submit the batch job that creates the delta changes data set.
  2. Import the delta changes data set as a new change on the test system. To import the promoted changes on the test system:
    1. Go the Change Management main menu on the test system and display the Manage Changes panel.
    2. Select the option to import changes.
    3. Specify the name of the delta changes data set to import into a change, and register the imported change in the Change Management database.
      Importing a change is a two-step process. First, Db2 Admin Tool performs an analysis to determine if there are any prerequisite changes that are pending for the objects that are affected by the imported change. Next, the change is registered. The steps can be performed either in the foreground (TSO) or the background (batch).
  3. Analyze the imported change. To analyze the change:
    1. Go to the Change Management main menu and display the list of changes.
    2. Issue the analyze command for the change.
    3. Submit the batch job that Db2 generates to perform the analyze.
      The batch job produces a report of the changes that will be made and generates a WSL that will make the changes.
  4. Run the imported change and capture a snapshot of the test human resources database after the change is complete. To run the change:
    1. Go to the Change Management main menu and display the list of changes.
    2. Issue the run command for the change, specifying that a new base version of the database structure should be created after the changes are made.
    3. Submit the batch job that runs the WSL that applies the changes.