When multiple load operations load data concurrently into the
same table, some load might fail with the -2038 error on a
partitioning subagent if the database partitions are not
specified by the PARTITIONING_DBPARTNUMS option.
If the database partitions are specified by the
PARTITIONING_DBPARTNUMS option and do not overlap, the issue can
be avoided.
The following is the failure that you may see.
$ db2 "load from TAB01.del.001 of del insert into TAB01 ( ID,
DATA ) indexing mode AUTOSELECT partitioned db config
OUTPUT_DBPARTNUMS ( 1,2 )"
$ db2 "load from TAB01.del.003 of del insert into TAB01 ( ID,
DATA ) indexing mode AUTOSELECT partitioned db config
OUTPUT_DBPARTNUMS ( 3,4 )"
The former LOAD command completes as follows.
Agent Type Node SQL Code Result
________________________________________________________________
______________
LOAD 001 +00000000 Success.
________________________________________________________________
______________
LOAD 002 +00000000 Success.
________________________________________________________________
______________
PARTITION 002 +00000000 Success.
________________________________________________________________
______________
PRE_PARTITION 001 +00000000 Success.
________________________________________________________________
______________
RESULTS: 2 of 2 LOADs completed successfully.
On the other hand, later one may fail as follows.
Agent Type Node SQL Code Result
________________________________________________________________
______________
PARTITION 002 -00002038 Error.
________________________________________________________________
______________
RESULTS: 0 of 0 LOADs completed successfully.
The following messages are logged in db2diag.log of node 3
during the problem reproduction.
2011-12-14-09.42.20.718989+540 I4296551A465 LEVEL: Warning
PID : 4784424 TID : 22761 PROC : db2sysc
3
INSTANCE: db2dpf NODE : 003 DB : DB2DPF
APPHDL : 3-13181 APPID: *N3.db2dpf.111214004220
AUTHID : DB2INST1
EDUID : 22761 EDUNAME: db2agent (DB2DPFA)
FUNCTION: DB2 UDB, database utilities, sqluvtld_route_in,
probe:839
DATA #1 : <preformatted>
Starting LOAD operation (S) (1) (I).
2011-12-14-09.42.20.884282+540 I4323019A573 LEVEL: Error
PID : 4784424 TID : 22761 PROC : db2sysc
3
INSTANCE: db2dpf NODE : 003 DB : DB2DPF
APPHDL : 3-13181 APPID: *N1.db2dpf.111214004220
AUTHID : DB2INST1
EDUID : 22761 EDUNAME: db2agent (DB2DPFA) 3
FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0
DATA #1 : String, 152 bytes
LOADID: 22761.2011-12-14-09.42.20.718978.3 (123;270)
Received error reply from catalog SA , -2038, 0, Detected in
file:sqlusMPPCoordinator.C, Line:1613
The following messages are logged in db2diag.log of node 1
during the problem reproduction.
2011-12-14-09.42.17.753584+540 I4347326A462 LEVEL: Warning
PID : 4719042 TID : 24360 PROC : db2sysc
1
INSTANCE: db2dpf NODE : 001 DB : DB2DPF
APPHDL : 1-14282 APPID: *N1.db2dpf.111214004217
AUTHID : DB2INST1
EDUID : 24360 EDUNAME: db2agent (DB2DPFA) 1
FUNCTION: DB2 UDB, database utilities, sqluvtld_route_in,
probe:839
DATA #1 : <preformatted>
Starting LOAD operation (S) (1) (I).
2011-12-14-09.42.17.900607+540 I4353501A488 LEVEL: Warning
PID : 9896200 TID : 20978 PROC : db2sysc
2
INSTANCE: db2dpf NODE : 002 DB : DB2DPF
APPHDL : 1-14282 APPID: *N1.db2dpf.111214004217
AUTHID : DB2INST1
EDUID : 20978 EDUNAME: db2lload 2
FUNCTION: DB2 UDB, database utilities, DIAG_NOTE, probe:0
DATA #1 : String, 77 bytes
LOADID: 24360.2011-12-14-09.42.17.753573.1 (123;270)
Load SA is running. 0, 0
2011-12-14-09.42.20.790458+540 I4374522A527 LEVEL: Warning
PID : 9896200 TID : 7923 PROC : db2sysc
2
INSTANCE: db2dpf NODE : 002 DB : DB2DPF
APPHDL : 3-13181 APPID: *N3.db2dpf.111214004220
AUTHID : DB2INST1
EDUID : 7923 EDUNAME: db2linit 2
FUNCTION: DB2 UDB, database utilities, DIAG_NOTE, probe:0
DATA #1 : String, 114 bytes
LOADID: 22761.2011-12-14-09.42.20.718978.3 (123;270)
Init SA is running, (status = 2) (action = 5) (op = I). 0, 0
2011-12-14-09.42.20.790711+540 I4375050A652 LEVEL: Error
PID : 9896200 TID : 7923 PROC : db2sysc
2
INSTANCE: db2dpf NODE : 002 DB : DB2DPF
APPHDL : 3-13181 APPID: *N3.db2dpf.111214004220
AUTHID : DB2INST1
EDUID : 7923 EDUNAME: db2linit 2
FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0
DATA #1 : String, 240 bytes
LOADID: 22761.2011-12-14-09.42.20.718978.3 (123;270)
Failed to lock partitioning resource. This may indicate an
attempt to concurrently execute multiple loads from the same
node. , -2146434951, 6e, Detected in file:sqlusInitSA.C,
Line:1261 |
