What's a sustained trap?
oxufufei 270003RT82 Visits (6945)
In some cases, you may see an EDU traps (e.g. with signal 11), FODC_Trapxxxxx folder is created in db2dump, the corresponding application receives SQL1224N indicates its connection is forced off, but the subsequent application(s) can still make connections to the database.
From db2diag.log, you can find:
1. Trap Sustainability Criteria Checking = true
2. Message indicates "EDU has been suspended"
All above suggest a sustained trap happened. The sustaining of traps in general depends on many things. After a sustained trap, the connection associated with the trapping agent should be forced off and receive error, the sustained traps do not hold up any other work.
Note that db2stop force will not be able to force the last suspended agent and it will hang in early versions(i.e. DB2 V9.7 FixPack 2 or earlier FixPacks, V9.8 FixPack 3 or earlier FixPacks). If db2stop force is hanging it is working as designed in these versions - though it should timeout and kill db2sysc after start_stop timeout(default 10 minutes).
The instruction of "Recovering from sustained traps" is in Information center: