Dropping exception table during a LOAD may cause the following
error message in db2diag.log and database down. (The problem
only happens when the drop table occurs within a small timing
window near the beginning of the LOAD.)
This APAR fix will make the load fail with an error indicating
the table has been dropped instead of a trap.
Regardless of APAR, the user should check if there isn't any
pending load using the exception table.
Before dropping the table, the LOAD should be terminated.
2015-05-28-11.33.35.814918+540 I27490452A449 LEVEL: Error
PID : 2392140 TID : 24853 PROC : db2sysc
0
INSTANCE: XXXX NODE : 000 DB : XXXX
APPHDL : 0-7208 APPID: *LOCAL.XXXX.150527130410
AUTHID : XXXX
EDUID : 24853 EDUNAME: db2agent (XXXX) 0
FUNCTION: DB2 UDB, data management, sqldGetTablePools,
probe:11685
MESSAGE : Table (pool:3;obj:5075) not found.
2015-05-28-11.33.35.824837+540 I27490902A1513 LEVEL: Error
PID : 2392140 TID : 24853 PROC : db2sysc
0
INSTANCE: XXXX NODE : 000 DB : XXXX
APPHDL : 0-7208 APPID: *LOCAL.XXXX.150527130410
AUTHID : XXXX
EDUID : 24853 EDUNAME: db2agent (XXXX) 0
FUNCTION: DB2 UDB, data management, sqldGetTablePools, probe:5
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x0900000008A4FB60 pdLog + 0xE4
[1] 0x0900000004B2B7E4 sqldGetTablePools__FP8sqeAgentiN22PiT5
+ 0x5A0
[2] 0x090000000676696C
@101@sqldCheckPools__FP8sqeAgentP14SQLP_LOCK_INFOiUsT3 + 0xB8
[3] 0x09000000067667E8
sqldCheckPools__FP8sqeAgentP14SQLP_LOCK_INFOiUsT3@glueB42 + 0x80
[4] 0x090000000573396C
sqldLockTable__FP8sqeAgentP14SQLP_LOCK_INFOUiUsi + 0x68
[5] 0x0900000008BAE0BC
sqldLockTable__FP8sqeAgentP14SQLP_LOCK_INFOUiUsi@glue5A1 + 0x80
[6] 0x0900000008BADEB8
sqldLockTableFixTCB__FP8sqeAgentUsT2UciN35UlT9T5PcT5T12_T5P14SQL
P_LOCK_INFOPP8SQLD_TCBUiT18_ + 0x3C
[7] 0x0900000005B71CF4
zLockExceptionTableFixTCBs__10sqluCTableFP8sqeAgentP14SQLP_LOCK_
INFOUsT3 + 0x160
[8] 0x0900000005B683FC
sqluRegisterLoadStart__FPUcT1iP8sqluvlcbUcT3P8sqeAgentP12SQLB_GL
OBALSP20sqlu_loadapi_load_cbP16sqluCCatalogInfoP7sqlubmhP9SQLP_
+ 0xCD0
[9] 0x0900000005B669A4
@148@sqluDirectTraffic__FP26sqluCLoadRequestDescriptorP8sqluvlcb
P8sqeAgentP12SQLB_GLOBALSP20sqlu_loadapi_load_cbP15sql_static_d
+ 0x390
2015-05-28-11.33.35.825388+540 I27492416A824 LEVEL: Error
PID : 2392140 TID : 24853 PROC : db2sysc
0
INSTANCE: XXXX NODE : 000 DB : XXXX
APPHDL : 0-7208 APPID: *LOCAL.XXXX.150527130410
AUTHID : XXXX
EDUID : 24853 EDUNAME: db2agent (XXXX) 0
FUNCTION: DB2 UDB, database utilities,
sqluCTable::zLockExceptionTableFixTCBs, probe:2971
MESSAGE : ZRC=0x8704007A=-2029780870=SQLD_REC_DELETED "DELETED
RECORD ID"
DATA #1 : LOADID, PD_TYPE_LOADID, 51 bytes
LOADID: 24853.2015-05-27-22.04.10.801509.0 (7;1731)
DATA #2 : File name, 12 bytes
sqluTarget.C
DATA #3 : String, 46 bytes
sqldLockTableFixTCB() failed (exception table)
DATA #4 : unsigned integer, 2 bytes
3
DATA #5 : unsigned integer, 2 bytes
5075
DATA #6 : Boolean, 1 bytes
true
...
2015-05-28-11.33.35.909775+540 E27511280A948 LEVEL:
Critical
PID : 2392140 TID : 24853 PROC : db2sysc
0
INSTANCE: XXXX NODE : 000 DB : XXXX
APPHDL : 0-7208 APPID: *LOCAL.XXXX.150527130410
AUTHID : XXXX
EDUID : 24853 EDUNAME: db2agent (XXXX) 0
FUNCTION: DB2 UDB, base sys utilities,
sqeLocalDatabase::MarkDBBad, probe:10
MESSAGE : ADM14001C An unexpected and critical error has
occurred:
"DBMarkedBad". The instance may have been shutdown as
a result.
"Automatic" FODC (First Occurrence Data Capture) has
been invoked and
diagnostic information has been recorded in directory
"/XXXX/FODC_DBMarkedBad_2015-05-28-11.33.35.906686_0000/".
Please look in this directory for detailed evidence
about what
happened and contact IBM support if necessary to
diagnose the
problem. |
