Migration reports

During a system migration, Optim™ High Performance Unload generates several message that provide the migration information reports.

These messages are:
  • INZU543I, which indicates on which host the load steps were started.
  • INZU539I, which provides row statistics of the load operations in case of a successful migration.
  • INZU540W, which is generated if any warnings have been detected by the load step (for example, if a NULL data is to be loaded in a not nullable column).
  • INZU541E, which is generated only if the load step detects serious errors that prevent Optim High Performance Unload from loading data.

Migration report example

You want to migrate a table that is named TEST from a 64-bit instance db2inst1 to a 64-bit instance that is named db2inst2. The db2nodes.cfg file of instance db2inst1 has the following contents:
0    M0 0
The db2nodes.cfg file of instance db2inst2 has the following contents:
6    M1 0
9    M1 1
The control file for migration contains the following clauses:
MIGRATE TABLESPACE
...
TARGET ENVIRONMENT (INSTANCE “db2inst2” ON “M1”)
If the migration is successful, Optim High Performance Unload generates a migration report that contains the following messages:
...
INZU464I HPU run step start    : 14:48:07.316.
INZU398I No unload to be done on M0
INZU543I HPU utility will perform load operations on M1 host.
INZU539I [M1] HPU utility has performed load into DB2INST2.TEST 
on database SAMPLE for instance db2inst2 : Report in DB2INST2.TEST.msg 
(Read 29, Skipped 0, Loaded 0, Rejected 0, Deleted 0, Commited 29)
INZU465I HPU run step end      : 14:48:13.986.
...