DB2 for z/OS Bulk Data Movement with an Image Copy Source
DB2 for z/OS Bulk Data Movement with an Image Copy Source
You can use a full image copy of a DB2 table space or table space partition as a data source for a PowerExchange bulk data movement session. To create a full image copy, use the DB2 COPY utility.
For example, assume that you want to materialize a target based on an existing DB2 source. You can take a full image copy of the DB2 source. Then use that image copy as input to a PowerCenter workflow for materializing the target. After target materialization is complete, you can use PowerExchange change data capture (CDC) to keep the source and target synchronized.
When you use a full image copy as a data source, you do not need to create a data map. Instead, you can use a relational source definition that you import for a DB2 table.
Also, you can use a FlashCopy image copy or sequential image copy as a data source. If you use a FlashCopy image copy, ensure that it is for a table space that contains a single table and is not a deprecated type of table space.
When you define PowerCenter session properties, set the properties that control which image copy to read. You can configure the PowerExchange Reader for DB2 Image Copy to read any of the following image copies:
The latest SHRLEVEL REFERENCE FULL image copy
An image copy that you specify
An image copy that was created on a different DB2 subsystem
If you create an image copy of a compressed table space, the compressed rows can be unloaded from the image copy data set only if the dictionary for decompression has been retrieved and assembled in the correct order.
For PowerExchange to successfully process an image copy data set, the information in the DB2 catalog that describes the table and the table space containing the table must reflect the exact state of the objects at the time when the image copy was created. DB2 allows some ALTER statements to be issued and then later implemented (materialized) by running the REORG utility. Thus, a mismatch can occur between the information in the DB2 catalog and the content of the most recent image copy of a table space. Before you use an image copy as a source for bulk data movement, you must verify that no ALTER statements have been issued against the table or table space since the image copy was created.