During a load operation in a partitioned database environment, message files are created by some of the load processes on the database partitions where they are being executed.
The message files store all information, warning, and error messages produced during the execution of the load operation. The load processes that produce message files that can be viewed by the user are the load agent, pre-partitioning agent, and partitioning agent. The content of the message file is only available after the load operation is finished.
You can connect to individual database partitions during a load operation and issue the LOAD QUERY command against the target table. When issued from the CLP, this command displays the contents of the load message files that currently reside on that database partition for the table that is specified in the LOAD QUERY command.
load from load.del of del replace into table1 partitioned db config
partitioning_dbpartnums (1)
This command initiates
a load operation that includes load agents running on database partitions
0, 1, 2, and 3; a partitioning agent running on database partition
1; and a pre-partitioning agent running on database partition 0. set client connect_node 0
connect to wsdb
load query table table1
set client connect_node 1
connect to wsdb
load query table table1
If a load operation is initiated through the db2Load API, the messages option (piLocalMsgFileName) must be specified and the message files are brought from the server to the client and stored for you to view.
For multi-partition database load operations initiated from the CLP, the message files are not displayed to the console or retained. To save or view the contents of these files after a multi-partition database load is complete, the MESSAGES option of the LOAD command must be specified. If this option is used, once the load operation is complete the message files on each database partition are transferred to the client machine and stored in files using the base name indicated by the MESSAGES option. For multi-partition database load operations, the name of the file corresponding to the load process that produced it is listed in the following table:
Process type | File name |
---|---|
Load Agent | <message-file-name>.LOAD.<dbpartition-number> |
Partitioning Agent | <message-file-name>.PART.<dbpartition-number> |
Pre-partitioning Agent | <message-file-name>.PREP.<dbpartition-number> |