Due to a small timing hole, the instance may trap with SIGSEGV
in monitoring code during database manager snapshot collection
and active AIC processing with the following stack:
@103@sqlm_process_progress_info + 0x138
@103@sqlm_write_utility_info + 0x54C
@103@sqlm_write_dbm_info + 0xFB4
sqlmonssagnt + 0xC00
sqlmonssbackend + 0x3D0
sqlesrvr + 0xC34
sqleMappingFnServer + 0x3E4
sqlerKnownProcedure + 0x348
sqlerCallDL + 0xB74
.sqljs_ddm_excsqlstt. + 0x57C
sqljsParseRdbAccessed + 0x74
.sqljsParse.fdpr.clone. + 0x15B4
@73@sqljsSqlam + 0x2D8
@73@sqljsDriveRequests + 0xB4
@73@sqljsDrdaAsInnerDriver + 0x45C
sqljsDrdaAsDriver + 0x21C
RunEDU + 0x584
EDUDriver + 0x13C
sqlzRunEDU + 0x10
sqloEDUEntry + 0x264
You should see AIC messages in the db2diag.log file around the
trap, for example:
2013-02-23-01.22.14.805053+000 E2425460A568 LEVEL:
Warning
PID : 7602402 TID : 17791 PROC :
db2sysc 33
INSTANCE: xxxx NODE : 033 DB : xxx
APPHDL : 33-25199 APPID: xxxx
AUTHID : xxxxx HOSTNAME: xxxx
EDUID : 17791 EDUNAME: db2taskp (xxx) 33
FUNCTION: DB2 UDB, AIC, aicRolloutIndexCleanup, probe:2280
MESSAGE : ADM9515I END async index cleanup on table "xxxx
.xxxx" (ID "20") and table space "xxxx" (ID "101").
2013-02-23-01.22.14.810891+000 E2426029A570 LEVEL:
Warning
PID : 7602402 TID : 17791 PROC :
db2sysc 33
INSTANCE: xxxx NODE : 033 DB : xxx
APPHDL : 33-25199 APPID: xxxx
AUTHID : xxxxx HOSTNAME: xxxx
EDUID : 17791 EDUNAME: db2taskp (xxxx) 33
FUNCTION: DB2 UDB, AIC, aicRolloutIndexCleanup, probe:2075
MESSAGE : ADM9514I BEGIN async index cleanup on table "xxxx
.xxxx" (ID "20") and table space "xxxx" (ID "101"). |
