Unanswered: Load error - SQL2038N A database system error "-902"
I´m trying to make multiple (concurrent) loads into a table distributed across multiple database partitions. IBM documentation says:
- Multiple load operations can load data into the same table concurrently if the partitions specified by the OUTPUT_DBPARTNUMS and PARTITIONING_DBPARTNUMS options do not overlap. For example, if a table is defined on partitions 0 through 3, one load operation can load data into partitions 0 and 1 while a second load operation can load data into partitions 2 and 3.
One load works well. When I try to run the second one I get the following error:
SQL2038N A database system error "-902" occurred during processing.
I found a SQL2038N which says "Examine the error code in the message for more information" but can not find description of system error code -902.
I´m using DB2 LUW 9.7.
The load command was:
db2 "load client from /dataset/myfile_part_1_2.dat of del modified by coldel} nochardel insert into SQ.MYTABLE NONRECOVERABLE PARTITIONED DB CONFIG MODE PARTITION_AND_LOAD PARTITIONING_DBPARTNUMS (1,2) OUTPUT_DBPARTNUMS (1,2)" > l1.txt&
db2 "load client from /dataset/myfile_part_3_4.dat of del modified by coldel} nochardel insert into SQ.MYTABLE NONRECOVERABLE PARTITIONED DB CONFIG MODE PARTITION_AND_LOAD PARTITIONING_DBPARTNUMS (3,4) OUTPUT_DBPARTNUMS (3,4)" > l2.txt&
[db2inst1@centos ~]$ db2 "? SQL0902"
SQL0902C A system error (reason code = "<reason-code>") occurred.
Subsequent SQL statements cannot be processed.
A system error occurred.
Record the message number (SQLCODE) and reason code in the message.
If trace was active, invoke the Independent Trace Facility at the
operating system command prompt. Then contact your technical service
representative with the following information:
* Problem description
* SQLCODE and embedded reason code
* SQLCA contents if possible
* Trace file if possible.
Federated system users: isolate the problem to the data source failing
the request (refer to the Troubleshooting Guide to determine which data
source is failing to process the SQL statement) and take the necessary
diagnostic steps for that data source. The problem determination
procedures for data sources vary, so refer to the applicable data source