Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see Recovery Management for Db2 13.1.

Moving data with a migration file

The 

Recovery Management for Db2

 solution provides a method for transferring all types of 

Some content is unavailable due to permissions.

 and IBM copies between Db2 subsystems.

The best method to use depends on whether DASD is shared between the two subsystems. With shared DASD, you can use the MIGRATE command to merge the source image copy with log and write the new image directly to the target table space. If the target site is remote, you can use the IMPORT command to move an image copy of the source table space to the target table space.

The MIGRATE and IMPORT commands can process several objects in one execution, an OBJECTSET, or a single table space or index. The table names in the migration file are matched to the table names on the execution subsystem. If the table names do not match, you can use the CHANGE FROM...TO option in the USING specification to make them match. All other attributes of the table must be the same.

Some content is unavailable due to permissions.

supports the EXPORT and IMPORT commands. For more information, see the ALTER and BMC AMI Change Manager for Db2.

Related topics

Solution-only-features

Using

 

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