When ran concurrently, the online incremental backup and data
load may cause DB2 to crash and dump the stack traces and agents
dump files to the DB2 diagnostic log path. Following entries
will typically appear in the db2diag.log file:
1. Start of Load operation:
2012-07-27-16.50.02.089000+120 I4682876F481 LEVEL: Warning
PID : 2040 TID : 9652 PROC :
db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : xxx
APPHDL : 0-27973 APPID: *LOCAL.DB2.120727130831
AUTHID : xxx
EDUID : 9652 EDUNAME: db2agent (xxx)
FUNCTION: DB2 UDB, database utilities, sqluvtld_route_in,
probe:839
DATA #1 : <preformatted>
Starting LOAD operation (S) (3) (I).
2. Start of online incremental delta backup
2012-07-27-18.30.59.410000+120 E4707301F477 LEVEL: Info
PID : 2040 TID : 9740 PROC :
db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : xxx
APPHDL : 0-29149 APPID: *LOCAL.DB2.120727163224
AUTHID : xxx
EDUID : 9740 EDUNAME: db2agent (xxx)
FUNCTION: DB2 UDB, database utilities, sqlubSetupJobControl,
probe:1604
MESSAGE : Starting an online incremental delta db backup.
3. DB2 crash :
2012-07-27-20.40.32.891000+120 I4709246F582 LEVEL: Severe
PID : 2040 TID : 4248 PROC :
db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : xxx
APPHDL : 0-29149 APPID: *LOCAL.DB2.120727163224
AUTHID : xxx
EDUID : 4248 EDUNAME: db2bm.9740.0 (xxx)
FUNCTION: DB2 UDB, RAS/PD component,
pdResilienceIsSafeToSustain, probe:800
DATA #1 : String, 37 bytes
Trap Sustainability Criteria Checking
DATA #2 : Hex integer, 8 bytes
0x2000000303008808
DATA #3 : Boolean, 1 bytes
false
Following stack will be produced for a failed agent:
sqmLockEvents::collectRequestorActivities
sqmLockEvents::collectLockEvent
sqlplnfd
sqlplrq
SqlubTableLock::request
sqlubReadSMS
sqlubBMCont
sqlubbuf
sqleSubCoordProcessRequest
sqeAgent::RunEDU
sqlzRunEDU
sqloEDUEntry |
