From the perspective of the migration program, the migration process consists of the following steps:
This section provides a brief overview of each step. Detailed information about the steps and command syntax are provided later in this chapter.
The collection step consists of gathering the existing Version 1 replication definitions into a DB2 migration database. This migration database contains several global control tables, two of which store registration and subscription information from all specified Version 1 servers.
You can repeat the collection step, each time generating a new version of the registration and subscription details for analysis.
The analysis step consists of analyzing the contents of the global control tables in the migration database to detect potential migration exceptions and make necessary adjustments.
The migration analysis step does the following:
After reading the migration report, you can decide whether the automated migration choices are appropriate. If not, you can override the program's results by using standard SQL to update the data in the global control tables. Then you can rerun the analysis step to validate the current migration instructions.
The migration step consists of reading the replication definitions from the migration database and Version 1 control tables, and migrating to Version 5 control table formats. The MIGRATE action migrates one source server, one target server, or one of each (source and target) at a time. Source server and target server are Version 5 terms that replace the DataPropagator Relational Version 1 terms of source server and target server. The Version 5 terminology is used throughout this chapter.
You can back out of Version 5 migration and return to Version 1. If you choose this action, the migration program reads the original Version 1 definitions from the original Version 1 tables and the log sequence numbers from the current Version 5 control tables.
After successful migration, you can drop unused Version 1 tables and views to restore disk space if needed by running MIGRATE with the CLEANUP action.