Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange Bulk Data Movement
  3. PowerExchange Listener
  4. Adabas Bulk Data Movement
  5. Datacom Bulk Data Movement
  6. DB2 for i5/OS Bulk Data Movement
  7. DB2 for Linux, UNIX, and Windows Bulk Data Movement
  8. DB2 for z/OS Bulk Data Movement
  9. IDMS Bulk Data Movement
  10. IMS Bulk Data Movement
  11. Microsoft SQL Server Bulk Data Movement
  12. Oracle Bulk Data Movement
  13. Sequential File Bulk Data Movement
  14. VSAM Bulk Data Movement
  15. Writing Data with Fault Tolerance
  16. Monitoring and Tuning Options

Bulk Data Movement Guide

Bulk Data Movement Guide

DB2 Unload Files as Bulk Data Sources

DB2 Unload Files as Bulk Data Sources

You can use a DB2 unload file as a data source for a PowerExchange bulk data movement. First create the unload file and then use it to add a data map that can be imported into PowerCenter. The data map uses the DB2UNLD access method.
To create a DB2 unload file, use any of the following IBM or BMC Software utilities:
  • DB2 for z/OS online REORG TABLESPACE utility with UNLOAD EXTERNAL
  • DB2 for z/OS online UNLOAD utility
  • DB2 for z/OS sample DSNTIAUL unload program
  • BMC UNLOAD PLUS for DB2
If you use the BMC UNLOAD PLUS for DB2 utility, the following utility options can result in errors:
  • If you use the AUTOTAG YES option, the utility adds a 4-byte field at the beginning of each output record for each SELECT statement. The DB2UNLD data map that you create based on the unload file does not include this 4-byte field, which causes subsequent fields to be mapped incorrectly. If you then import the data map into PowerCenter for a PWX Batch session and try to run the session, the session fails. To avoid this problem either do not use the AUTOTAG YES option or manually add a 4-byte field at the beginning of each data map.
  • If you use the FIXEDVARCHAR NO option, the PowerExchange Navigator issues mapping errors when it tries to access the unload file to generate a data map. To avoid this problem, generate the unload file with the FIXEDVARCHAR YES option.
If you use the DB2 Version 11 REORG TABLESPACE utility with UNLOAD EXTERNAL, the NOPAD option is used by default. This option causes variable-length columns in the unloaded records to have the actual data length, without padding. When the PowerExchange Navigator tries to access the unload file to generate a data map, record mapping errors occur. To avoid this problem, generate the unload file with the NOPAD NO option.
For information about adding a data map based on an unload file, see the
PowerExchange Navigator User Guide
.

0 COMMENTS

We’d like to hear from you!