Viewing DB2 Object Data in the Investigator › How to Migrate DB2 Objects › Migrate DB2 Objects

Migrate DB2 Objects

Changes in applications often force the supporting database to change. As a DBA, you are constantly adding and modifying the data and infrastructure and moving and reorganizing data to adapt to changing business processes. Database migration replicates database objects, databases, security, and data between DB2 subsystems or within the same DB2 subsystem. During migration, you can implement changes to database objects in the new environment and can have the target environment adopt certain changes and attribute differences from the source environment.

The following list provides examples of when database objects must be migrated:

• To use a database or objects in a database, as the basis for a new database
• To move the test object changes into production
• To copy a database before you implement changes or for disaster recovery purposes

The Object Migrator wizard in CA Chorus for DB2 Database Management generates scripts that analyze the migration request and then migrate objects from one DB2 environment to another. The migration can be customized by choosing which objects to include, analyzing the migration request, and specifying the global changes to apply to the target environment. The wizard lets you migrate DB2 catalog objects avoiding JCL changes and syntax errors. You can use the wizard to perform up to 100 jobs simultaneously.

Follow these steps:

1. Navigate to the DB2 catalog object that you want to migrate, and highlight one or more rows of data.
2. Select Migrate under Navigation in the Actions pane.

   The Object Migrator wizard opens to the Select objects page.

3. Set up the migration:
   1. Review the DB2 object selections, and click Next.

      Note: If necessary, delete any objects that you want to exclude from the migration before you click Next.

      The Specify Analysis Options dialog opens and displays the source LPAR, DB2 subsystem identifier, and SQLID associated with the selected objects.

   2. Specify analysis options, and click Next.

      The analysis options include a description for the migration, selection of the target system where the data is migrated, and selection of the profile you created previously. The profile selection is optional.

      The Specify Migration Changes dialog opens. From this dialog, you can specify global changes on the target system by object type and attribute. These changes can help ensure that objects in the target systems adopt a specific naming convention. The changes also predefine attributes such as the segment size, data capture changes, CLOSE, buffer pool, and so on.

   3. (Optional) Define object changes by object type and attribute that you want to apply globally on the target system.

      The global changes help to verify that new objects on the target system adopt a naming convention. The global changes also help ensure that predefined attributes are applied (such as the SEGSIZE, data capture changes, CLOSE, buffer pool, and so on).

4. Submit the migration for analysis:
   1. Click Submit.

      The migration is submitted for analysis and the View Analysis Status dialog opens. This dialog provides the submitted analysis statement status.

   2. View the status and information about the current analysis requests:
      1. When the status changes to Completed or Error, click Next.

         The analysis produces migration control statements to perform the migration and the Migration Control Statements dialog opens. These controls statements identify the objects for migration and any dependencies while preserving the target data.

      2. Review messages about the analysis and review and edit the results.

         When an analysis shows that the migration would produce unintended results, you can customize the migration and can repeat the analysis until the migration produces the desired results.

5. Execute the migration:
   1. Click Submit to execute the migration control statements.

      If you edited the migration control statements, you are prompted to confirm the changes before execution. Otherwise, the View Migration Status dialog opens and displays the status details about the submitted migration statements. When the status changes to Completed, the migration results are displayed for review.

   2. Review the results and click Finish to complete the migration.

      The selected DB2 objects are migrated.

   You have successfully evaluated a migration candidate, built an analysis profile, and migrated DB2 objects.