If a LOAD operation into a table with XML column was interrupted
(or failed for any reason) while the load was in BUILD phase,
LOAD RESTART should not be allowed to continue the load
operation; we must do LOAD TERMINATE to abort the load and then
retry the original LOAD INSERT or LOAD REPLACE. Currently, we
incorrectly allow LOAD RESTART in some cases, and subsequent
operations on the table might encounter index error - SQLI_NOKEY
"Key not found within node". You might see similar messages to
the following in db2diag.log:
2012-02-17-13.31.39.158682-300 I9063911E542 LEVEL:
Severe
PID : 472 TID : 47264743549248 PROC :
db2sysc 1
INSTANCE: svtdbm2 NODE : 001 DB :
ABSINTHE
APPHDL : 0-1769 APPID:
9.26.98.0.58882.120217185546
AUTHID : SVTDBM2 HOSTNAME: vmsvtlnx64x09
EDUID : 1663 EDUNAME: db2agntp (ABSINTHE) 1
FUNCTION: DB2 UDB, index manager, procLeaf2Del, probe:2
DATA #1 : Hexdump, 4 bytes
0x00002AFCAE3FC264 : 2C00 0987
,...
2012-02-17-13.31.39.159917-300 I9066244E540 LEVEL:
Severe
PID : 472 TID : 47264743549248 PROC :
db2sysc 1
INSTANCE: svtdbm2 NODE : 001 DB :
ABSINTHE
APPHDL : 0-1769 APPID:
9.26.98.0.58882.120217185546
AUTHID : SVTDBM2 HOSTNAME: vmsvtlnx64x09
EDUID : 1663 EDUNAME: db2agntp (ABSINTHE) 1
FUNCTION: DB2 UDB, index manager, sqlischd, probe:973
DATA #1 : Hexdump, 4 bytes
0x00002AFCAE3FC518 : 2C00 0987
,...
2012-02-17-13.31.39.160248-300 I9066785E1581 LEVEL:
Severe
PID : 472 TID : 47264743549248 PROC :
db2sysc 1
INSTANCE: svtdbm2 NODE : 001 DB :
ABSINTHE
APPHDL : 0-1769 APPID:
9.26.98.0.58882.120217185546
AUTHID : SVTDBM2 HOSTNAME: vmsvtlnx64x09
EDUID : 1663 EDUNAME: db2agntp (ABSINTHE) 1
FUNCTION: DB2 UDB, index manager, sqlischd, probe:973
RETCODE : ZRC=0x8709002C=-2029453268=SQLI_NOKEY "Key not found
within node"
DIA8541C The index key could not be found, the value
was "".
DATA #1 : String, 11 bytes
blatch_mode
DATA #2 : signed integer, 4 bytes
3
DATA #3 : String, 11 bytes
lkey_option
DATA #4 : signed integer, 4 bytes
8
DATA #5 : String, 11 bytes
lsn_changed
DATA #6 : signed integer, 4 bytes
0
DATA #7 : String, 10 bytes
node_level
DATA #8 : signed integer, 4 bytes
1
DATA #9 : String, 14 bytes
recursive_call
DATA #10: signed integer, 4 bytes
0
DATA #11: String, 5 bytes
retry
DATA #12: signed integer, 4 bytes
0
DATA #13: String, 9 bytes
saved_lsn
DATA #14: SQLP_LSN8, PD_TYPE_SQLP_LSN8, 8 bytes
00000000070D6552
DATA #15: String, 8 bytes
slotinfo
DATA #16: Hexdump, 40 bytes
0x00002AFCAE3FC4F0 : 0600 0000 0000 0000 1A00 0000 0000 0000
................
0x00002AFCAE3FC500 : 0200 0000 0000 0000 1A00 0000 0000 0000
................
0x00002AFCAE3FC510 : 0100 0000 0000 0000
........
DATA #17: String, 7 bytes
pagenum
DATA #18: unsigned integer, 4 bytes
139
DATA #19: String, 9 bytes
currlevel
DATA #20: signed integer, 2 bytes
1
PID : 472 TID : 47264743549248 PROC :
db2sysc 1
INSTANCE: svtdbm2 NODE : 001 DB :
ABSINTHE
APPHDL : 0-1769 APPID:
9.26.98.0.58882.120217185546
AUTHID : SVTDBM2 HOSTNAME: vmsvtlnx64x09
EDUID : 1663 EDUNAME: db2agntp (ABSINTHE) 1
FUNCTION: DB2 UDB, index manager, sqliDumpPageFromAllMembers,
probe:20
MESSAGE : ADM14005E The following error occurred: "IndexError".
First
Occurrence Data Capture (FODC) has been invoked in the
following
mode: "Automatic". Diagnostic information has been
recorded in the
directory named
"/home/svtdbm2/sqllib/db2dump/FODC_IndexError_2012-02-17-13.31.3
9.161
967_472_1663_001/".
With this APAR fix, LOAD RESTART will be correctly blocked (with
SQL20054 reason code 30) in the above situation.
Note that in general, an online load or a load with copy yes
option that failed in a phase later than BUILD phase,
nonetheless can only restart in BUILD phase. Therefore if the
above XML LOAD is also an online load and/or use the copy yes
option, then LOAD RESTART will also be blocked. |
