This article details the DB2 KEEPFENCED and FENCED POOL configuration parameters.
DPA for DB2 uses IBM functions that are executed as fenced mode processes on the DB2 database. Routines run as fenced mode processes are executed in a separate memory space from the database server in order to isolate the code from the database manager process. The DB2 database configuration parameters KEEPFENCED and FENCED_POOL determine whether or not fenced mode processes are kept after a call to a fenced routine completes.
The number of fenced mode processes in the pool is determine by the configuration parameter FENCED_POOL. If FENCED_POOL is set to 0, then pooling is disabled and the value of KEEPFENCED is ignored. FENCED_POOL defaults to MAX_COORDAGENTS which should be sufficient in most cases.
SolarWinds recommends setting KEEPFENCED to YES to avoid the overhead of creating and destroying fenced mode processses. Setting KEEPFENCED to YES also works around some known bugs in the DB2 fenced mode processes infrastructure. The trade off is additional memory overhead on the server due to the additional cached processses.
You should try setting KEEPFENCED to YES in the following cases: