Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > DB2 KEEPFENCED and FENCED POOL configuration parameters

DB2 KEEPFENCED and FENCED POOL configuration parameters

Updated March 27, 2018


This article details the DB2 KEEPFENCED and FENCED POOL configuration parameters.


  • All versions of DPA


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.


  • If KEEPFENCED is set to NO, a separate fenced mode process is created and destroyed on every call to a fenced routine.
  • If KEEPFENCED is set to YES, fenced mode processses are pooled and reused for multiple calls to fenced routines. 


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:

  • You are getting unexplained connection errors when attempting to monitor a DB2 database.
  • You see errors or warnings in db2diag.log referring to fmp, db2fmp, or thread/process creation.
  • You see high CPU usage on the DB2 database server when monitoring with DPA.
Last modified