Example: Migration execution limited to the Db2 Load part with already distributed data

This example shows the report of an execution that is limited to the Db2 Load side of an automatic migration, with files that have data already distributed for the target. Optim™ High Performance Unload is run against a Db2 instance that has two logical database partitions on the same unique machine. The database partition numbers are 0 and 1. The target table is in the same database and Db2 instance, which is not mandatory for such a scenario.

Note: The files to be loaded exist before the Optim High Performance Unload execution, and their names are suitable for a Db2 Load step that runs against already distributed streams. Even if it is not shown as expected, these files contain a header with a partition map at the beginning. The header and map are mandatory for such a scenario.


[i975@lat186(:) hm500_mnt]$ ls -al outfile.00*
-rw-r--r-- 1 i975 db2grp 10422 Sep 12 19:06 outfile.000
-rw-r--r-- 1 i975 db2grp 11354 Sep 12 19:06 outfile.001

[i975@lat186(:) hm500_mnt]$ db2hpu -f SYSIN -i i975 --load-only
INZM031I Optim High Performance Unload for Db2 06.01.00.001(120912) 64 bits 09/12/2012 (Linux lat186 x86_64)
INZI473I Memory limitations: 'unlimited' for virtual memory and 'unlimited' for data segment
       ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----10---+----11---+----12---+----13-
000001 GLOBAL CONNECT TO SAMPLE;
000002 MIGRATE TABLESPACE
000003 SELECT * FROM EMPLOYEE;
000004 TARGET KEYS (DEFAULT)
000005 TARGET ENVIRONMENT (INSTANCE "i975")
000006 OUTFILE("outfile")
000007 FORMAT DEL INTO EMP_TARGET
000008 ;
000009

INZU462I HPU control step start: 19:07:40.382.
INZU463I HPU control step end  : 19:07:40.771.
INZU464I HPU run step start    : 19:07:40.797.
INZU605I The execution is limited to the loading data-related processing.
INZU543I HPU utility will perform load operations on lat186 host.
INZU539I [lat186] HPU utility has performed load (INSERT mode) into I975.EMP_TARGET on database SAMPLE for instance i975 : 
         Report in /home/i975/labo/hm500_mnt/I975.EMP_TARGET.msg (Read 42, Skipped 0, Loaded 42, Rejected 0, Deleted 0, Commited 42)
INZU465I HPU run step end      : 19:07:47.934.
INZI441I HPU successfully ended: Real time -> 0m7.551867s
User time -> 0m0.016997s : Parent -> 0m0.016997s, Children -> 0m0.000000s
Syst time -> 0m0.008998s : Parent -> 0m0.008998s, Children -> 0m0.000000s