Data Migration

Specify Source

To specify the source, use an existing Access Definition or create a new Access Definition. The created Access Definition can be temporary, for a single use, or permanent, saved for repeated use. The Access Definition is used as input to the Extract Process. (See the Common Elements Manual for a detailed discussion of creating and modifying Access Definitions.)

The Extract Process copies the specified data and object definitions (i.e., table, view, key, index, etc.) to an Extract File. The Extract File is saved and can be reused as needed.

Specify Destination

The Insert Process copies the source data and object definitions to a destination. Move offers flexibility for changing the destination specification or automatically inserting the data and object definitions in a logical manner.

For example, if the destination tables do not exist, Move provides the option of creating DB2 or Legacy tables to match the source before inserting the data. If the named destination tables do exist but do not match the source DB2 or Legacy tables, you can use Column Maps to specify exactly what data is placed in each column. This includes the source data, literal values, special registers, expressions, exit routines and DB2 defaults. (See the Common Elements Manual for detailed discussions.)

Legacy Tables

Legacy Tables allow you to process certain IMS™, VSAM or sequential data as if it were stored in DB2 tables. Any reference to a table in this section applies to a Legacy Table, unless indicated otherwise.

Materialized Query Tables

A Materialized Query Table (MQT) is a DB2 table used to hold the results of a query against one or more tables. User-maintained MQTs are modifiable and System-maintained MQTs are protected. References to tables in this section apply to MQTs, unless stated otherwise.