A migration file that the BMC AMI Copy EXPORT command creates facilitates the migration. You run the EXPORT command on the target subsystem to collect information on one or more target table spaces. This information includes object identifiers and other information relating to the target table spaces. You run the BMC AMI Recover MIGRATE command on the source subsystem to migrate all the table spaces to the target table spaces that are identified by the command. The INDEP OUTSPACE specification is required in order to specify the target VSAM data set model name. Prior to executing the MIGRATE command, the target table spaces must be stopped.
BMC AMI Recover requires consistent use of the INDEP OUTSPACE option across all commands; if you use INDEP OUTSPACE with one command, you must use it with all other commands that support it. If you use INDEP OUTSPACE but subsequently omit it from another command that supports it, BMC AMI Recover issues an error message.
The MIGRATE command queries the source SYSCOPY and BMCXCOPY tables for the required image copy, and then merges the copy with log (if requested) and translates object identifiers to create the target image. The log information can come from Db2 log and change accumulation files. If you specify FROMRBA, only log is used for the migration.
This command requires one of the following valid passwords:
A Recovery Management for Db2 solution password
A Database Administration for DB2 solution password
The Database Administration (DAD) password allows BMC AMI Recover to perform data migration functions that were generated by BMC AMI Change Manager for Db2 within a worklist, but does not include full-function BMC AMI Recover.
For more information about copy migration using BMC AMI Copy EXPORT and BMC AMI Recover MIGRATE, see Using MIGRATE and IMPORT for data movement and .
The following figures show the syntax of the MIGRATE command:
MIGRATE command dependencies and prohibitions
The MIGRATE command has the following limitations:
No support for copies of the Db2 catalog
No support for specifying DSNUM
When selecting image copies, the MIGRATE command uses a DSNUM 0 copy or DSNUM n copies. DSNUM n copies will only be considered when all the partitions or data sets are registered at the same log point.
No support for rebuilding migrated indexes
However, BMC AMI Recover can recover any indexes in the migration data set depending on the value of the INDEXES parameter in the USING clause. If the source and target table spaces or index spaces are not at the same version, you will need to run REPAIR VERSIONS on the target system after the MIGRATE is executed. If the indexes for a versioned space were not migrated, then these indexes would need to be rebuilt in a separate step on the target system.
No support for migrating LOB or XML spaces
BMC AMI Recover cannot migrate LOB or XML spaces when the base table space is a partition-by-growth (PBG) space and there are fewer partitions on the target than on the source. In this case, adding partitions to the base table space on the target system causes BMC AMI Recover to create new auxiliary table spaces, but these new table spaces will not be present in the migration file.
The following table describes the common dependencies for coding the MIGRATE command.
Option that must be used
FROMRBA or FROMLOGPOINT
TORBA or TOLOGPOINT
The following table describes the common prohibitions to coding the MIGRATE commands:
Option that must not be used
MIGRATE option descriptions
The following options are available with MIGRATE:
- USING specification
- TABLESPACE specification
- FROMRBA or FROMLOGPOINT specification for MIGRATE
- OBJECTSET specification for MIGRATE
- INDEPENDENT OUTSPACE specification for MIGRATE
- TORBA or TOLOGPOINT specification for MIGRATE
- TOCOPY LASTCOPY specification
- LOGSORT specification for MIGRATE
- LOGAPPLY ONLY for MIGRATE
- LOGONLY for MIGRATE
- CLONE for MIGRATE
- ANALYZE for MIGRATE
Not all of the options described are valid in a single MIGRATE command. The recovery strategy that best meets your needs determines which options you should include in a single command statement.