Load Agent (db2agent) might miss a message sent from Load Ridder
(db2lrid) when the load is about to end in a rare
timing-dependent scenario, so that it mistakenly believes that
Load Ridder has gone without notifying it, then fails with
SQL2043N.
Once you hit the issue, you can see the following error messages
from db2diag.log right after the last completed load phase
(LOAD, BUILD or other phases that depend on your load case):
2013-06-29-00.37.27.283000+120 I13314651F616 LEVEL: Error
PID : 2984 TID : 9076 PROC :
db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SAMPLE
APPHDL : 0-15928 APPID: *LOCAL.DB2
.130628223256
AUTHID : #JOBSCHEDULERDB2ADM
EDUID : 9076 EDUNAME: db2agent (SAMPLE)
FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0
DATA #1 : String, 163 bytes
LOADID: 9076.2013-06-29-00.32.52.292000.0 (945;4)
Load EDU has unexpected died or was killed , -2029059911,
0000000000000FC0, Detected in file:sqluvld.C, Line:3996
2013-06-29-00.37.27.829000+120 I13317437F1044 LEVEL: Error
PID : 2984 TID : 9076 PROC :
db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SAMPLE
APPHDL : 0-15928 APPID: *LOCAL.DB2
.130628223256
AUTHID : #JOBSCHEDULERDB2ADM
EDUID : 9076 EDUNAME: db2agent (SAMPLE)
FUNCTION: DB2 UDB, database utilities, sqlulPollMsg, probe:4011
MESSAGE : ZRC=0x8015006D=-2146107283=SQLU_CA_BUILT
"SQLCA has already been built"
DATA #1 : LOADID, PD_TYPE_LOADID, 49 bytes
LOADID: 9076.2013-06-29-00.32.52.292000.0 (945;4)
DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -2043 sqlerrml: 0
sqlerrmc:
sqlerrp : SQLUVLD
sqlerrd : (1) 0x8015006D (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0x00000000 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: |
