The EXPORT and IMPORT commands

The EXPORT command runs on the sending subsystem during phase 1 of the migration to collect information on one or more table spaces. This information includes object identifiers, the names of image copies, and other information relating to the sending table spaces. The EXPORT command includes this information in a sequential migration file.

The IMPORT command runs on the receiving subsystem during phase 2 of the migration to migrate all the image copy data to the receiving table space that is identified by the command. The IMPORT command uses the object identifiers found in the EXPORT command’s migration file and translates them to the object identifiers found in the receiving catalog.

The EXPORT and IMPORT commands comprise the Copy Migration feature of the Recovery Management and Database Administration solutions. When you use the Copy Migration feature, the following requirements must be met:

• You must have a valid BMC Database Administration for DB2, BMC AMI Database Administration for Db2, BMC AMI Recovery for Db2, Next Generation Technology Database Administration for DB2, or Recovery Management for Db2 solution password.
• No structural changes to the table or table space exist.
• Objects must be migrated at the table space level.
• The IBM IMPDSDEF subsystem parameter must be set to YES. (If the parameter is set to NO and the data set does not exist on the receiving subsystem, BMC AMI Recover fails.)
• An existing registered local primary copy data set must exist.

When you select BMC AMI Copy EXPORT/BMC AMI Recover IMPORT to analyze your migrate-type work ID , the product uses the BMC AMI Copy and BMC AMI Recover utilities and inserts the COPYEXPORT keyword into the ALUIN input stream. When the work ID is analyzed, Analysis inserts the -BMCC and -BMCV commands into the worklist.

When you use the Copy Migration feature:

• The feature supports the migration of LOB data from the image copies of the LOB table spaces.
• The feature supports the migration of XML data from the image copies of the XML table spaces.
• The EXPORT command always uses the most current version of either SHRLEVEL REFERENCE or SHRLEVEL CHANGE image copies.
• When an image copy contains auxiliary table spaces, Change Manager invokes the IBM CHECK LOB utility. The CHECK LOB utility identifies inconsistencies in the auxiliary table spaces and invalid LOB values.
• To migrate history table spaces, you must explicitly include them in the scope.
• When an image copy contains a clone table, Change Manager generates separate EXPORT and IMPORT commands for the base table and the clone table.
• The feature supports objects that are defined in an implicit database or table space. The table space must not be defined with DEFINE NO.
• The feature supports the migration of a simple table space.
• The feature supports the migration of indexes.

This section contains the following topics: