Implementation of a migration strategy
The following scenario provides examples of how you can prepare for structure recovery, and one method for establishing and maintaining an application over several subsystems.
The USA Credit company has data centers in Austin, Texas and Dallas, Texas. Recently, the company expanded operations and needs to set up a new site in Houston, Texas. Db2 application development is maintained in Austin, while the Dallas and Houston sites are maintained as production-only environments.
As the database administrator, you must have the current version of the new application up and running in Houston and Dallas by the end of the week. The safest and most efficient method to create the same Db2 data structures in Houston as those in Austin is to perform a migration process. The test subsystem in Austin is the control point for defining data structure definitions and implementing subsequent versions of the application. In this instance, the Austin site is acting as a strong sender.
When you establish the application in Houston, you also want to automate the application of certain changes. You know, for example, that you want the database name and the table names in Houston to use a different naming convention than the ones used in Austin. You also want to be sure that you move a specific set of data structures. In addition, you know that some changes to the application are planned in the coming months, and when the application is in test and running smoothly you will want to migrate the changes to the application to Houston again.
Preparation before establishing and maintaining the application
Preparation can be divided into two categories of activities:
- Establishing the application on another subsystem
- Moving changes from the control node to the receiving subsystems on an ongoing basis
In planning to properly establish the application, you perform the following tasks:
- Create the catalog baseline profile and the migrate profile.
- Establish a baseline of the current application version.
- Perform a full migration process to establish the application in Houston.
In the future, after you have made changes to the application and want to apply these changes to the application across several subsystems, you perform the following tasks:
- Establish a baseline of the changed application.
- Perform a change migration process.
Use of an outbound migrate profile
An outbound migrate profile provides a means of control when performing a migration process and a change migration process.
You can define the scope of the outbound migrate profile to select the same Db2 object structures each time the migration is performed. The change rules that are defined for the outbound migrate profile can ensure the implementation of the Houston naming conventions consistently.
This section contains the following topic:
Related topic