Defining target objects for migration

In order to successfully migrate data from a source image copy to a target space, the source and target object definitions must be identical.

You cannot change any of the characteristics of the table space or tables that affect their internal structure. Target index definitions can differ if the target indexes are to be rebuilt rather than recovered from a source image copy.

Related topics

Migrating-data

Moving-an-application-to-another-subsystem-with-index-recovery


Important

When you are performing a migration, the source definition must match the target definition, including the number of partitions. For the migration of a partition-by-growth (PBG) universal spaces where the number of source data sets differs from the number of target data sets, BMC AMI Recover determines the number of source data sets and acts accordingly.

You can obtain the object definitions by using a tool such as one of the following BMC products: BMC AMI Catalog Manager for Db2, ALTER for Db2, or BMC AMI Change Manager for Db2. (If you use BMC AMI Change Manager for Db2, it can systematically change object names using a name mask in a migrate profile, which could be helpful if many table spaces are involved).

If you have a Recovery Management for Db2 solution password, Change Manager supports the EXPORT and IMPORT commands (not MIGRATE) of the Copy Migration feature. For more information, see the ALTER and BMC AMI Change Manager for Db2and the Recovery Management for Db2 documentation.

It is important to be aware of any alterations to source definitions. For example, assume Source_Table_A has been defined with 5 fixed-length columns. Subsequently, Source_Table_A is altered to add a variable-length column and the source image copy is created before a REORG is executed. Defining Target_Table_A with 6 columns (5 fixed-length and 1 variable-length) and using the source image copy for migration will result in a data incompatibility error (00C90101) when trying to access the target data. In this case, Target_Table_A needs to be defined with 5 fixed-length columns and then altered to add the variable-length column. (If you use BMC AMI Change Manager for Db2, it will identify these types of changes to source objects and build target definition and actions appropriately).

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*